Banking systems controlled by data bearing records

ABSTRACT

A cash handling device having at least one processor, a communication interface, an item accepting device, an item dispensing device, an internal currency scanning system, an internal currency transport system, one or more currency storage cartridges, and a memory may receive, from a user, a request to perform a deposit transaction. Based on receiving the request to perform the deposit transaction, the cash handling device may receive at least one deposit item for deposit. Subsequently, the cash handling device may validate the at least one deposit item received for deposit. Based on validating the at least one deposit item received for deposit, the cash handling device may generate a deposit transaction record that includes information directing a banking server to apply a provisional credit to a treasury account associated with the user. Subsequently, the cash handling device may send the deposit transaction record to the banking server.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and is a continuation of U.S.patent application Ser. No. 15/686,478, filed Aug. 25, 2017, andentitled “Banking Systems Controlled by Data Bearing Records,” whichclaims the benefit of and is a continuation of U.S. patent applicationSer. No. 15/130,063, filed Apr. 15, 2016, and entitled “Banking SystemsControlled by Data Bearing Records.” Each of the foregoing applicationsis incorporated by reference herein in its entirety.

BACKGROUND

Aspects of the disclosure relate to banking systems controlled by databearing records. In particular, one or more aspects of the disclosurerelate to utilizing cash handling devices to provide treasury functions,including deposit functions and change order functions, and implementinga computing platform to control a plurality of cash handling devices.

Cash handling devices may be used in operating centers and otherlocations to provide various functions that, in some instances, mayotherwise be provided by personnel. Deploying and utilizing thesedevices may provide many benefits to clients, including increasedconvenience, security, and efficiency. In many instances, however, itmay be difficult to integrate such cash handling devices with thetechnical infrastructure that supports banking operations and otheroperations while also optimizing the efficient and effective technicaloperations of the cash handling devices and various related computersystems.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, andconvenient technical solutions that address and overcome the technicalproblems associated with utilizing cash handling devices to providetreasury functions and implementing a computing platform to control aplurality of cash handling devices.

In accordance with one or more embodiments, a cash handling devicehaving at least one processor, a communication interface, an itemaccepting device, an item dispensing device, and a memory may receive,from a first user of the cash handling device, a request to perform adeposit transaction at a deployment location of the cash handlingdevice. Based on receiving the request to perform the deposittransaction at the deployment location of the cash handling device, thecash handling device may receive, via the item accepting device, atleast one deposit item for deposit at the deployment location of thecash handling device. Subsequently, the cash handling device mayvalidate the at least one deposit item received for deposit at thedeployment location of the cash handling device. Based on validating theat least one deposit item received for deposit at the deploymentlocation of the cash handling device, the cash handling device maygenerate a deposit transaction record associated with the request toperform the deposit transaction, and the deposit transaction record mayinclude deposit information directing at least one banking server toapply a provisional credit to at least one treasury account associatedwith the first user of the cash handling device. Subsequently, the cashhandling device may send, via the communication interface, and to the atleast one banking server, the deposit transaction record. Thereafter,the cash handling device may receive, from a second user of the cashhandling device, a request to perform a change order transaction at thedeployment location of the cash handling device. Based on receiving therequest to perform the change order transaction at the deploymentlocation of the cash handling device, the cash handling device mayreceive, via the item accepting device, at least one change order itemfor exchange at the deployment location of the cash handling device.Subsequently, the cash handling device may validate the at least onechange order item received for exchange at the deployment location ofthe cash handling device. Based on validating the at least one changeorder item received for exchange at the deployment location of the cashhandling device, the cash handling device may dispense, via the itemdispensing device, one or more currency items to complete the changeorder transaction. Subsequently, the cash handling device may generate achange order transaction record associated with the request to performthe change order transaction, and the change order transaction recordmay include change order information directing the at least one bankingserver to update one or more transaction history records associated withthe second user of the cash handling device. Then, the cash handlingdevice may send, via the communication interface, and to the at leastone banking server, the change order transaction record.

In some embodiments, the cash handling device further may include aninternal currency scanning system, an internal currency transportsystem, and one or more currency storage cartridges. In addition,validating the at least one deposit item received for deposit at thedeployment location of the cash handling device may include: scanning,by the internal currency scanning system, one or more deposit itemsreceived for deposit; sorting, by the internal currency transportsystem, the one or more deposit items received for deposit; andphysically storing, by the internal currency transport system, in theone or more currency storage cartridges, the one or more deposit itemsreceived for deposit. In addition, validating the at least one changeorder item received for exchange at the deployment location of the cashhandling device may include: scanning, by the internal currency scanningsystem, one or more change order items received for exchange; sorting,by the internal currency transport system, the one or more change orderitems received for exchange; and physically storing, by the internalcurrency transport system, in the one or more currency storagecartridges, the one or more change order items received for exchange.

In some embodiments, the deployment location of the cash handling devicemay be a retail banking center operated by a financial institution. Inother embodiments, the deployment location of the cash handling devicemay be a shopping mall in which a plurality of retailers operate retailstores.

In some embodiments, the at least one deposit item received for depositmay include one or more currency notes. In some embodiments, the atleast one deposit item received for deposit may include one or morecurrency coins. In some embodiments, the at least one deposit itemreceived for deposit may include one or more checks.

In some embodiments, the deposit information may directs the at leastone banking server to credit the at least one treasury accountassociated with the first user of the cash handling device with anamount of funds associated with the at least one deposit item receivedfor deposit at the deployment location of the cash handling device andvalidated by the cash handling device.

In some embodiments, the at least one change order item received forexchange may include one or more currency notes. In some embodiments,the at least one change order item received for exchange may include oneor more currency coins.

In some embodiments, the cash handling device may receive, from a thirduser of the cash handling device, input defining one or moreconfiguration settings for the cash handling device. Subsequently, thecash handling device may store configuration information based onreceiving the input defining the one or more configuration settings forthe cash handling device from the third user of the cash handlingdevice.

In some embodiments, the cash handling device may receive, via thecommunication interface, and from the at least one banking server,configuration information defining one or more configuration settingsfor the cash handling device. Subsequently, the cash handling device maystore the configuration information defining the one or moreconfiguration settings for the cash handling device received from the atleast one banking server.

In some embodiments, configuration information stored by the cashhandling device may define one or more usage limits. In some instances,validating the at least one deposit item received for deposit at thedeployment location of the cash handling device may include enforcingthe one or more usage limits defined by the configuration informationstored by the cash handling device. In addition, validating the at leastone change order item received for exchange at the deployment locationof the cash handling device may include enforcing the one or more usagelimits defined by the configuration information stored by the cashhandling device.

In some embodiments, configuration information stored by the cashhandling device may define one or more alert thresholds. In someinstances, validating the at least one deposit item received for depositat the deployment location of the cash handling device may includegenerating at least one deposit alert based on the one or more alertthresholds defined by the configuration information stored by the cashhandling device. In addition, validating the at least one change orderitem received for exchange at the deployment location of the cashhandling device may include generating at least one exchange alert basedon the one or more alert thresholds defined by the configurationinformation stored by the cash handling device.

In some embodiments, the cash handling device may receive, via thecommunication interface, and from the at least one banking server, userprofile information defining one or more user settings for the cashhandling device. Subsequently, the cash handling device may store theuser profile information defining the one or more user settings for thecash handling device received from the at least one banking server.

In some embodiments, prior to receiving the request to perform thedeposit transaction at the deployment location of the cash handlingdevice, the cash handling device may authenticate the first user of thecash handling device based on the user profile information defining theone or more user settings for the cash handling device received from theat least one banking server. In addition, prior to receiving the requestto perform the change order transaction at the deployment location ofthe cash handling device, the cash handling device may authenticate thesecond user of the cash handling device based on the user profileinformation defining the one or more user settings for the cash handlingdevice received from the at least one banking server.

In some embodiments, based on validating the at least one deposit itemreceived for deposit at the deployment location of the cash handlingdevice, the cash handling device may provide a deposit receiptassociated with the request to perform the deposit transaction. Inaddition, based on validating the at least one change order itemreceived for exchange at the deployment location of the cash handlingdevice, the cash handling device may provide an exchange receiptassociated with the request to perform the change order transaction.

In some embodiments, the deposit transaction record may includeinformation identifying one or more denominations of currency receivedby the cash handling device, one or more quantities of specificdenominations of currency received by the cash handling device, a timeat which the deposit transaction was completed, a user that performedthe deposit transaction, a quantity of deposit items rejected, and oneor more destination accounts into which currency was deposited.

In accordance with one or more additional and/or alternativeembodiments, a computing platform having at least one processor, amemory, and a communication interface may receive, via the communicationinterface, and from one or more cash handling devices, aggregatedactivity information comprising a plurality of transaction records.Subsequently, the computing platform may identify one or more deposittransactions based on the aggregated activity information comprising theplurality of transaction records received from the one or more cashhandling devices. Based on identifying the one or more deposittransactions based on the aggregated activity information comprising theplurality of transaction records received from the one or more cashhandling devices, the computing platform may generate one or moreaccount credit commands, and the one or more account credit commands maydirect at least one account management computer system to apply one ormore provisional credits to one or more treasury accounts associatedwith the one or more deposit transactions. Subsequently, the computingplatform may send, via the communication interface, to the at least oneaccount management computer system, the one or more account creditcommands directing the at least one account management computer systemto apply the one or more provisional credits to the one or more treasuryaccounts associated with the one or more deposit transactions.

In some embodiments, the plurality of transaction records received fromthe one or more cash handling devices may include informationidentifying, for each transaction, a specific user who performed thetransaction, an amount of currency involved in the transaction, a timeat which the transaction occurred, and a specific cash handling deviceon which the transaction was performed.

In some embodiments, receiving the aggregated activity information mayinclude: receiving, via the communication interface, and from a firstcash handling device of the one or more cash handling devices, firstactivity information comprising a first plurality of transaction recordsassociated with transactions performed by the first cash handlingdevice; and receiving, via the communication interface, and from asecond cash handling device of the one or more cash handling devices,second activity information comprising a second plurality of transactionrecords associated with transaction performed by the second cashhandling device.

In some instances, the first cash handling device may be located at afirst deployment location, and the second cash handling device may belocated at a second deployment location different from the firstdeployment location.

In some instances, the first deployment location may be a retail bankingcenter operated by a financial institution, and the second deploymentlocation may be a shopping mall in which a plurality of retailersoperate retail stores.

In some embodiments, the computing platform may generate a client alertmessage based on the aggregated activity information comprising theplurality of transaction records received from the one or more cashhandling devices. Subsequently, the computing platform may send, via thecommunication interface, to a client computing device, the client alertmessage generated based on the aggregated activity informationcomprising the plurality of transaction records received from the one ormore cash handling devices.

In some embodiments, the computing platform may generate an internalalert message based on the aggregated activity information comprisingthe plurality of transaction records received from the one or more cashhandling devices. Subsequently, the computing platform may send, via thecommunication interface, to an administrative computing device, theinternal alert message generated based on the aggregated activityinformation comprising the plurality of transaction records receivedfrom the one or more cash handling devices.

In some embodiments, the computing platform may evaluate a currencylevel indicative of an amount of currency stored in a first cashhandling device of the one or more cash handling devices. Subsequently,the computing platform may identify a restocking need based onevaluating the currency level indicative of the amount of currencystored in the first cash handling device of the one or more cashhandling devices. Based on identifying the restocking need, thecomputing platform may generate a restocking request, and the restockingrequest may direct a transport agent to restock the first cash handlingdevice of the one or more cash handling devices. Subsequently, thecomputing platform may send, via the communication interface, to atransport computer system, the restocking request directing thetransport agent to restock the first cash handling device of the one ormore cash handling devices.

In some embodiments, the computing platform may receive, via thecommunication interface, from an administrative computing device, arequest for an administrative portal. Based on receiving the request forthe administrative portal, the computing platform may provide, via thecommunication interface, to the administrative computing device, atleast one administrative interface. Subsequently, the computing platformmay receive, via the communication interface, from the administrativecomputing device, configuration input defining one or more configurationsettings for at least one cash handling device of the one or more cashhandling devices. Such configuration input may have been received by theadministrative computing device via the at least one administrativeinterface. Thereafter, the computing platform may send, via thecommunication interface, and to the at least one cash handling device ofthe one or more cash handling devices, configuration informationdirecting the at least one cash handling device of the one or more cashhandling devices to implement the one or more configuration settings.

In some embodiments, the computing platform may receive, via thecommunication interface, from a client computing device, a request for aclient management portal. Based on receiving the request for the clientmanagement portal, the computing platform may provide, via thecommunication interface, to the client computing device, at least oneclient management interface. Subsequently, the computing platform mayreceive, via the communication interface, from the client computingdevice, configuration input defining one or more configuration settingsfor at least one cash handling device of the one or more cash handlingdevices. Such configuration input may have been received by the clientcomputing device via the at least one client management interface.Thereafter, the computing platform may send, via the communicationinterface, and to the at least one cash handling device of the one ormore cash handling devices, configuration information directing the atleast one cash handling device of the one or more cash handling devicesto implement the one or more configuration settings.

In some embodiments, the computing platform may generate one or morereports based on the aggregated activity information comprising theplurality of transaction records received from the one or more cashhandling devices. Subsequently, the computing platform may provide, viathe communication interface, to at least one computing device, the oneor more reports generated based on the aggregated activity informationcomprising the plurality of transaction records received from the one ormore cash handling devices.

In some embodiments, the computing platform may receive, via thecommunication interface, from an administrative computing device,reconciliation information associated with at least one deposittransaction completed at the one or more cash handling devices. Based onreceiving the reconciliation information associated with the at leastone deposit transaction completed at the one or more cash handlingdevices, the computing platform may generate one or more account updatecommands, and the one or more account update commands may direct the atleast one account management computer system to convert at least onepreviously-applied provisional credit to non-provisional credit.Subsequently, the computing platform may send, via the communicationinterface, to the at least one account management computer system, theone or more account update commands directing the at least one accountmanagement computer system to convert the at least onepreviously-applied provisional credit to non-provisional credit.

In accordance with one or more additional and/or alternativeembodiments, a cash handling device having at least one processor, acommunication interface, an item accepting device, an item dispensingdevice, an internal currency scanning system, an internal currencytransport system, one or more currency storage cartridges, and a memorymay receive, from a first user of the cash handling device, a request toperform a deposit transaction at a deployment location of the cashhandling device. Based on receiving the request to perform the deposittransaction at the deployment location of the cash handling device, thecash handling device may receive, via the item accepting device, atleast one deposit item for deposit at the deployment location of thecash handling device. Subsequently, the cash handling device mayvalidate the at least one deposit item received for deposit at thedeployment location of the cash handling device. Based on validating theat least one deposit item received for deposit at the deploymentlocation of the cash handling device, the cash handling device maygenerate a deposit transaction record associated with the request toperform the deposit transaction, the deposit transaction recordcomprising deposit information directing at least one banking server toapply a provisional credit to at least one treasury account associatedwith the first user of the cash handling device. Subsequently, the cashhandling device may send, via the communication interface, and to the atleast one banking server, the deposit transaction record.

In some embodiments, validating the at least one deposit item receivedfor deposit at the deployment location of the cash handling device mayinclude: scanning, by the internal currency scanning system, one or moredeposit items received for deposit; sorting, by the internal currencytransport system, the one or more deposit items received for deposit;and physically storing, by the internal currency transport system, inthe one or more currency storage cartridges, the one or more deposititems received for deposit.

In some embodiments, the cash handling device may receive, from a seconduser of the cash handling device, a request to perform a change ordertransaction at the deployment location of the cash handling device.Based on receiving the request to perform the change order transactionat the deployment location of the cash handling device, the cashhandling device may receive, via the item accepting device, at least onechange order item for exchange at the deployment location of the cashhandling device. Subsequently, the cash handling device may validate theat least one change order item received for exchange at the deploymentlocation of the cash handling device. Based on validating the at leastone change order item received for exchange at the deployment locationof the cash handling device, the cash handling device may dispense, viathe item dispensing device, one or more currency items to complete thechange order transaction. Subsequently, the cash handling device maygenerate a change order transaction record associated with the requestto perform the change order transaction, the change order transactionrecord comprising change order information directing the at least onebanking server to update one or more transaction history recordsassociated with the second user of the cash handling device. Thereafter,the cash handling device may send, via the communication interface, andto the at least one banking server, the change order transaction record.

In some embodiments, validating the at least one change order itemreceived for exchange at the deployment location of the cash handlingdevice may include: scanning, by the internal currency scanning system,one or more change order items received for exchange; sorting, by theinternal currency transport system, the one or more change order itemsreceived for exchange; and physically storing, by the internal currencytransport system, in the one or more currency storage cartridges, theone or more change order items received for exchange.

In some instances, the deployment location of the cash handling devicemay be a retail banking center operated by a financial institution. Insome instances, the deployment location of the cash handling device maybe a shopping mall in which a plurality of retailers operate retailstores. In some instances, the at least one deposit item received fordeposit may include one or more currency notes. In some instances, theat least one deposit item received for deposit may include one or morecurrency coins. In some instances, the at least one deposit itemreceived for deposit may include one or more checks. In some instances,the at least one change order item received for exchange may include oneor more currency notes. In some instances, the at least one change orderitem received for exchange may include one or more currency coins.

In some embodiments, the deposit information may direct the at least onebanking server to credit the at least one treasury account associatedwith the first user of the cash handling device with an amount of fundsassociated with the at least one deposit item received for deposit atthe deployment location of the cash handling device and validated by thecash handling device.

In some embodiments, the cash handling device may receive, from a thirduser of the cash handling device, input defining one or moreconfiguration settings for the cash handling device. Subsequently, thecash handling device may store configuration information based onreceiving the input defining the one or more configuration settings forthe cash handling device from the third user of the cash handlingdevice.

In some embodiments, the cash handling device may receive, via thecommunication interface, and from the at least one banking server,configuration information defining one or more configuration settingsfor the cash handling device. Subsequently, the cash handling device maystore the configuration information defining the one or moreconfiguration settings for the cash handling device received from the atleast one banking server.

In some embodiments, configuration information stored by the cashhandling device may define one or more usage limits. In addition,validating the at least one deposit item received for deposit at thedeployment location of the cash handling device may include enforcingthe one or more usage limits defined by the configuration informationstored by the cash handling device. In addition, validating the at leastone change order item received for exchange at the deployment locationof the cash handling device may include enforcing the one or more usagelimits defined by the configuration information stored by the cashhandling device.

In some embodiments, configuration information stored by the cashhandling device may define one or more alert thresholds. In addition,validating the at least one deposit item received for deposit at thedeployment location of the cash handling device may include generatingat least one deposit alert based on the one or more alert thresholdsdefined by the configuration information stored by the cash handlingdevice. In addition, validating the at least one change order itemreceived for exchange at the deployment location of the cash handlingdevice may include generating at least one exchange alert based on theone or more alert thresholds defined by the configuration informationstored by the cash handling device.

In some embodiments, the cash handling device may receive, via thecommunication interface, and from the at least one banking server, userprofile information defining one or more user settings for the cashhandling device. Subsequently, the cash handling device may store theuser profile information defining the one or more user settings for thecash handling device received from the at least one banking server.

In some embodiments, prior to receiving the request to perform thedeposit transaction at the deployment location of the cash handlingdevice, the cash handling device may authenticate the first user of thecash handling device based on the user profile information defining theone or more user settings for the cash handling device received from theat least one banking server. In addition, prior to receiving the requestto perform the change order transaction at the deployment location ofthe cash handling device, the cash handling device may authenticate thesecond user of the cash handling device based on the user profileinformation defining the one or more user settings for the cash handlingdevice received from the at least one banking server.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A, 1B, and 1C depict an illustrative computing environment forutilizing cash handling devices to provide treasury functions andimplementing a computing platform to control a plurality of cashhandling devices in accordance with one or more example embodiments;

FIGS. 2A-2M depict an illustrative event sequence for utilizing cashhandling devices to provide treasury functions and implementing acomputing platform to control a plurality of cash handling devices inaccordance with one or more example embodiments;

FIGS. 3A-3H depict another illustrative event sequence for utilizingcash handling devices to provide treasury functions and implementing acomputing platform to control a plurality of cash handling devices inaccordance with one or more example embodiments;

FIGS. 4-13 depict example graphical user interfaces for utilizing cashhandling devices to provide treasury functions and implementing acomputing platform to control a plurality of cash handling devices inaccordance with one or more example embodiments;

FIG. 14 depicts an illustrative method for utilizing cash handlingdevices to provide treasury functions and implementing a computingplatform to control a plurality of cash handling devices in accordancewith one or more example embodiments;

FIG. 15 depicts another illustrative method for utilizing cash handlingdevices to provide treasury functions and implementing a computingplatform to control a plurality of cash handling devices in accordancewith one or more example embodiments; and

FIG. 16 depicts another illustrative method for utilizing cash handlingdevices to provide treasury functions and implementing a computingplatform to control a plurality of cash handling devices in accordancewith one or more example embodiments.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

FIGS. 1A, 1B, and 1C depict an illustrative computing environment forutilizing cash handling devices to provide treasury functions andimplementing a computing platform to control a plurality of cashhandling devices in accordance with one or more example embodiments.Referring to FIG. 1A, computing environment 100 may include one or morecomputing devices. For example, computing environment 100 may include anaccount management computer system 120, an administrative computingdevice 130, a treasury device support server 150, a treasury clientcomputing device 160, and a transport carrier computer system 170.

Account management computer system 120 may be configured to store and/ormaintain account information for one or more customers of anorganization. For instance, account management computer system 120 maybe configured to store and/or maintain account information for one ormore customers of a financial institution, including one or morenon-commercial customers, one or more treasury clients (which may, e.g.,be retailers, restaurants, and/or other small businesses), and/or one ormore other clients. Administrative computing device 130 may beconfigured to provide one or more interfaces that allow forconfiguration and management of one or more other computing devicesand/or computer systems included in computing environment 100.

Treasury device support server 150 may be configured to communicate withand support the operations of one or more cash handling devices that maybe included in computing environment 100, for instance, by aggregatingactivity information received from various cash handling devices andcommunicating such aggregated activity information to one or moreservers and/or computing platforms, as discussed in greater detailbelow. Treasury client computing device 160 may be configured to be usedby a client of an organization, such as a treasury client of a financialinstitution. Transport carrier computer system 170 may be configured tobe used by a transport agent or other transport carrier entity, whichmay restock one or more cash handling devices, as discussed in greaterdetail below.

In one or more arrangements, account management computer system 120,administrative computing device 130, treasury device support server 150,treasury client computing device 160, and transport carrier computersystem 170 may be any type of computing device capable of receiving auser interface, receiving input via the user interface, andcommunicating the received input to one or more other computing devices.For example, account management computer system 120, administrativecomputing device 130, treasury device support server 150, treasuryclient computing device 160, and transport carrier computer system 170may, in some instances, be and/or include server computers, desktopcomputers, laptop computers, tablet computers, smart phones, or the likethat may include one or more processors, memories, communicationinterfaces, storage devices, and/or other components. As noted above,and as illustrated in greater detail below, any and/or all of accountmanagement computer system 120, administrative computing device 130,treasury device support server 150, treasury client computing device160, and transport carrier computer system 170 may, in some instances,be special-purpose computing devices configured to perform specificfunctions.

Computing environment 100 also may include one or more computingplatforms. For example, computing environment 100 may include treasuryservice computing platform 110. As illustrated in greater detail below,treasury service computing platform 110 may include one or morecomputing devices configured to perform one or more of the functionsdescribed herein. For example, treasury service computing platform 110may include one or more computers (e.g., laptop computers, desktopcomputers, servers, server blades, or the like).

Computing environment 100 also may include one or more cash handlingdevices. For example, computing environment 100 may include treasuryservice cash handling device 140. As illustrated in greater detailbelow, treasury service cash handling device 140 may include one or morecomputing devices and/or other components configured to perform one ormore of the functions described herein. For example, treasury servicecash handling device 140 may include various components configured toenable treasury service cash handling device 140 to accept deposits ofcurrency (which may, e.g., be made by treasury clients and/or othernon-consumer clients of a financial institution, such as one or moreretailers, small businesses, or the like), process change ordertransactions in which an amount of currency in a first set ofdenominations is exchanged for an amount of currency in a second,different set of denominations, and/or perform other functions, asdiscussed in greater detail below.

Computing environment 100 also may include one or more networks, whichmay interconnect one or more of treasury service computing platform 110,account management computer system 120, administrative computing device130, treasury service cash handling device 140, treasury device supportserver 150, treasury client computing device 160, and transport carriercomputer system 170. For example, computing environment 100 may includepublic network 190 and private network 195. Private network 195 and/orpublic network 190 may include one or more sub-networks (e.g., localarea networks (LANs), wide area networks (WANs), or the like). Privatenetwork 195 may be associated with a particular organization (e.g., acorporation, financial institution, educational institution,governmental institution, or the like) and may interconnect one or morecomputing devices associated with the organization. For example,treasury service computing platform 110, account management computersystem 120, and administrative computing device 130 may be associatedwith an organization (e.g., a financial institution), and privatenetwork 195 may be associated with and/or operated by the organization,and may include one or more networks (e.g., LANs, WANs, virtual privatenetworks (VPNs), or the like) that interconnect treasury servicecomputing platform 110, account management computer system 120, andadministrative computing device 130 and one or more other computingdevices and/or computer systems that are used by, operated by, and/orotherwise associated with the organization. Public network 190 mayconnect private network 195 and/or one or more computing devicesconnected thereto (e.g., treasury service computing platform 110,account management computer system 120, and administrative computingdevice 130) with one or more networks and/or computing devices that arenot associated with the organization. For example, treasury service cashhandling device 140, treasury device support server 150, treasury clientcomputing device 160, and transport carrier computer system 170 mightnot be associated with an organization that operates private network 195(e.g., because treasury service cash handling device 140, treasurydevice support server 150, treasury client computing device 160, andtransport carrier computer system 170 may be owned, operated, and/orserviced by one or more entities different from the organization thatoperates private network 195, such as one or more customers of theorganization and/or vendors of the organization, rather than being ownedand/or operated by the organization itself or an employee or affiliateof the organization), and public network 190 may include one or morenetworks (e.g., the internet) that connect treasury service cashhandling device 140, treasury device support server 150, treasury clientcomputing device 160, and transport carrier computer system 170 toprivate network 195 and/or one or more computing devices connectedthereto (e.g., treasury service computing platform 110, accountmanagement computer system 120, and administrative computing device130).

Referring to FIG. 1B, treasury service computing platform 110 mayinclude one or more processors 111, memory 112, and communicationinterface 115. A data bus may interconnect processor(s) 111, memory 112,and communication interface 115. Communication interface 115 may be anetwork interface configured to support communication between treasuryservice computing platform 110 and one or more networks (e.g., privatenetwork 195, public network 190, or the like). Memory 112 may includeone or more program modules having instructions that when executed byprocessor(s) 111 cause treasury service computing platform 110 toperform one or more functions described herein and/or one or moredatabases that may store and/or otherwise maintain information which maybe used by such program modules and/or processor(s) 111. In someinstances, the one or more program modules and/or databases may bestored by and/or maintained in different memory units of treasuryservice computing platform 110 and/or by different computing devicesthat may form and/or otherwise make up treasury service computingplatform 110. For example, memory 112 may have, store, and/or include atreasury service module 113 and a treasury service database 114.Treasury service module 113 may have instructions that direct and/orcause treasury service computing platform 110 to manage and/or control aplurality of cash handling devices and/or perform other functions, asdiscussed in greater detail below. Treasury service database 114 maystore information used by treasury service module 113 and/or treasuryservice computing platform 110 in managing and/or controlling cashhandling devices and/or in performing other functions.

Referring to FIG. 1C, treasury service cash handling device 140 mayinclude one or more processors 141, memory 142, item accepting device145, item dispensing device 146, currency scanning system 147 a,currency transport system 147 b, storage cartridges 147 c, andcommunication interface 148. Item accepting device 145 may include oneor more slots, trays, rollers, scanners, scales, and/or processing unitsthat may be configured to receive, accept, and/or reject one or morecurrency notes, coins, checks, and/or other items (e.g., from a user oftreasury service cash handling device 140). Item dispensing device 146may include one or more slots, trays, rollers, scanners, scales, and/orprocessing units that may be configured to output and/or dispense one ormore currency notes, coins, and/or other items (e.g., to a user oftreasury service cash handling device 140). In some instances, itemaccepting device 145 and item dispensing device 146 may be incorporatedinto and/or physically integrated with treasury service cash handlingdevice 140, while in other instances, item accepting device 145 and itemdispensing device 146 may be standalone devices that are physicallyseparated from each other and controlled by treasury service cashhandling device 140. Currency scanning system 147 a may include one ormore scanners and/or rollers that may be configured to scan one or morecurrency notes, coins, checks, and/or other items. Currency transportsystem 147 b may include one or more rollers and/or stackers that may beconfigured to move, organize, and/or store currency (e.g., withintreasury service cash handling device 140 and/or in one or morecartridges). Storage cartridges 147 c may include one or more currencynotes and/or coins and may be used by treasury service cash handlingdevice 140 to store and/or hold currency of various denominations and/orother items received and/or dispensed by treasury service cash handlingdevice 140.

Communication interface 148 may be a network interface configured tosupport communication between treasury service cash handling device 140and one or more networks (e.g., private network 195, public network 190,or the like). Memory 142 may include one or more program modules havinginstructions that when executed by processor(s) 141 cause treasuryservice cash handling device 140 to perform one or more functionsdescribed herein and/or one or more databases that may store and/orotherwise maintain information which may be used by such program modulesand/or processor(s) 141. In some instances, the one or more programmodules and/or databases may be stored by and/or maintained in differentmemory units of treasury service cash handling device 140 and/or bydifferent computing devices that may form and/or otherwise make uptreasury service cash handling device 140. For example, memory 142 mayhave, store, and/or include a cash handling module 143 and a cashhandling database 144. Cash handling module 143 may have instructionsthat direct and/or cause treasury service cash handling device 140 toprocess one or more transactions, including deposit transactions and/orchange order transactions, and/or perform other functions, as discussedin greater detail below. Cash handling database 144 may storeinformation used by cash handling module 143 and/or treasury servicecash handling device 140 in processing transactions and/or in performingother functions.

In some arrangements, treasury service cash handling device 140 may beconfigured to operate as a cash recycling device (which may, e.g., alsobe referred to as a “cash recycler” and/or a “currency recycler”), suchthat currency items (e.g., notes, coins, and/or the like) which aredeposited at treasury service cash handling device 140 may be laterdispensed by treasury service cash handling device 140 without firstbeing transported to a financial institution, banking center, or otherlocation remote from treasury service cash handling device 140 formanual sorting and/or verification. In these arrangements, treasuryservice cash handling device 140 may thus recycle currency items, forinstance, by dispensing currency that was previously deposited attreasury service cash handling device 140. For example, treasury servicecash handling device 140 may receive and store one or more currencyitems in storage cartridges 147 c during a first transaction (which may,e.g., be a deposit transaction), and then during a second transaction(which may, e.g., be a withdrawal transaction or a change ordertransaction), treasury service cash handling device 140 may dispense thesame one or more currency items from storage cartridges 147 c. In thisexample, the first transaction and the second transaction may beperformed by different users of treasury service cash handling device140 who may, for instance, be associated with different treasury clientsof a financial institution operating treasury service cash handlingdevice 140. In other arrangements, treasury service cash handling device140 might not be configured to operate as a cash recycling device. Insuch arrangements, treasury service cash handling device 140 may storecurrency items received in connection with one or more deposittransactions in a first set of storage cartridges, and treasury servicecash handling device 140 may store currency items for dispensing inconnection with one or more withdrawal transactions and/or change ordertransactions in a second set of storage cartridges different from thefirst set of storage cartridges. For example, in arrangements in whichtreasury service cash handling device 140 is not configured to operateas a cash recycling device, treasury service cash handling device 140may keep deposited currency separate from other currency that is storedby treasury service cash handling device 140 for purposes of dispensing.

FIGS. 2A-2M depict an illustrative event sequence for utilizing cashhandling devices to provide treasury functions and implementing acomputing platform to control a plurality of cash handling devices inaccordance with one or more example embodiments. As discussed in greaterdetail below, the event sequence shown in FIGS. 2A-2M illustrates, amongother things, how a cash handling device, such as treasury service cashhandling device 140, may be configured, as well as how the cash handlingdevice may authenticate one or more users, process one or moretransactions, and provide updates to treasury service computing platform110, treasury device support server 150, and/or one or more otherservers or devices.

Referring to FIG. 2A, at step 201, treasury service cash handling device140 may initiate an item accepting device. For example, at step 201,treasury service cash handling device 140 may power on item acceptingdevice 145 and/or one or more components of item accepting device 145,initiate one or more connections to and/or with item accepting device145 and/or one or more components of item accepting device 145, andbegin executing one or more event monitoring threads to monitor itemaccepting device 145 and/or one or more components of item acceptingdevice 145. At step 202, treasury service cash handling device 140 mayinitiate an item dispensing device. For example, at step 202, treasuryservice cash handling device 140 may power on item dispensing device 146and/or one or more components of item dispensing device 146, initiateone or more connections to and/or with item dispensing device 146 and/orone or more components of item dispensing device 146, and beginexecuting one or more event monitoring threads to monitor itemdispensing device 146 and/or one or more components of item dispensingdevice 146. At step 203, treasury service cash handling device 140 mayinitiate one or more server connections. For example, at step 203,treasury service cash handling device 140 may establish connections toand/or with treasury service computing platform 110 and/or treasurydevice support server 150. Additionally or alternatively, treasuryservice cash handling device 140 may notify treasury service computingplatform 110 and/or treasury device support server 150 that treasuryservice cash handling device 140 is online and/or that item acceptingdevice 145 and/or item dispensing device 146 have been initiated.

After initiating various devices, components, and/or connections,treasury service cash handling device 140 may receive and/or storeconfiguration information based on input received from a user oftreasury service cash handling device 140, as illustrated in greaterdetail below. Such input and/or configuration information may, forinstance, identify the location of treasury service cash handling device140 (e.g., at a specific banking center, at a specific shopping mall, ina particular geographic region, and/or the like), specify one or moreusage limits for treasury service cash handling device 140 (e.g.,maximum deposit limits, change order restrictions, compliance limits,bank-imposed limits, client-imposed limits, and/or the like), and/orspecify one or more alert thresholds for treasury service cash handlingdevice 140 (e.g., restocking alerts, security alerts, and/or the like).

At step 204, treasury service cash handling device 140 may present oneor more configuration interfaces. For example, at step 204, treasuryservice cash handling device 140 may display and/or otherwise presentone or more graphical user interfaces to a user of treasury service cashhandling device 140 that may be configured to allow the user of treasuryservice cash handling device 140 to define various configurationparameters, preferences, and/or other settings controlling operation ofand/or otherwise affecting treasury service cash handling device 140.Referring to FIG. 2B, at step 205, treasury service cash handling device140 may receive input via the one or more configuration interfaces. Forexample, at step 205, treasury service cash handling device 140 mayreceive, from a user of the cash handling device (e.g., treasury servicecash handling device 140), input defining one or more configurationsettings for the cash handling device (e.g., treasury service cashhandling device 140). The input defining the one or more configurationsettings for the cash handling device (e.g., treasury service cashhandling device 140) may, for instance, define one or more usage limits,alert thresholds, and/or other settings for the cash handling device(e.g., treasury service cash handling device 140). At step 206, treasuryservice cash handling device 140 may store configuration information(e.g., based on the input received via the one or more configurationinterfaces). For example, at step 206, treasury service cash handlingdevice 140 may store configuration information based on receiving theinput defining the one or more configuration settings for the cashhandling device (e.g., treasury service cash handling device 140) fromthe user of the cash handling device (e.g., treasury service cashhandling device 140).

In addition to or instead of receiving configuration information and/orcorresponding input from a user of treasury service cash handling device140, treasury service cash handling device 140 may receive and/or storeconfiguration information from treasury service computing platform 110.Such configuration information may be received directly from treasuryservice computing platform 110 and/or may be received via treasurydevice support server 150. Additionally or alternatively, theconfiguration information received by treasury service cash handlingdevice 140 from treasury service computing platform 110 may be similarto the configuration information and/or corresponding input receivedfrom the user of treasury service computing platform 110. For example,the configuration information received from treasury service computingplatform 110 may, for instance, identify the location of treasuryservice cash handling device 140 (e.g., at a specific banking center, ata specific shopping mall, in a particular geographic region, and/or thelike), specify one or more usage limits for treasury service cashhandling device 140 (e.g., maximum deposit limits, change orderrestrictions, compliance limits, bank-imposed limits, client-imposedlimits, and/or the like), and/or specify one or more alert thresholdsfor treasury service cash handling device 140 (e.g., restocking alerts,security alerts, and/or the like). In some instances, treasury servicecash handling device 140 may be configured to only receive configurationinformation from treasury service computing platform 110 (e.g., and notfrom a user of treasury service cash handling device 140), while inother instances, treasury service cash handling device 140 may beconfigured to only receive configuration information from a user oftreasury service cash handling device 140 (e.g., and not from treasuryservice computing platform 110).

At step 207, treasury service computing platform 110 may provide one ormore configuration interfaces (e.g., to administrative computing device130, treasury client computing device 160, and/or one or more othercomputing devices). For example, at step 207, treasury service computingplatform 110 may generate and/or send (e.g., to administrative computingdevice 130, treasury client computing device 160, and/or one or moreother computing devices) one or more graphical user interfaces that maybe configured to allow a user (e.g., of administrative computing device130, treasury client computing device 160, or another computing device)to define various configuration parameters, preferences, and/or othersettings controlling operation of and/or otherwise affecting treasuryservice cash handling device 140. In providing the one or moreconfiguration interfaces to administrative computing device 130 and/ortreasury client computing device 160, treasury service computingplatform 110 may cause, control, and/or direct administrative computingdevice 130 and/or treasury client computing device 160 to display and/orotherwise present a graphical user interface similar to graphical userinterface 400, which is illustrated in FIG. 4. As seen in FIG. 4,graphical user interface 400 may include one or more user interfacecontrols and/or other elements that may enable a user of administrativecomputing device 130 and/or treasury client computing device 160interacting with graphical user interface 400 to define one or moreusage limits for a cash handling device, such as treasury service cashhandling device 140. Such usage limits may, for instance, include afirst maximum deposit amount for a first client, a second maximumdeposit amount for a second client (which may, e.g., be different fromthe first maximum deposit amount for the first client), a maximum changeorder amount for a third client, and/or additional usage limits.

Additionally or alternatively, in providing the one or moreconfiguration interfaces to administrative computing device 130 and/ortreasury client computing device 160, treasury service computingplatform 110 may cause, control, and/or direct administrative computingdevice 130 and/or treasury client computing device 160 to display and/orotherwise present a graphical user interface similar to graphical userinterface 500, which is illustrated in FIG. 5. As seen in FIG. 5,graphical user interface 500 may include one or more user interfacecontrols and/or other elements that may enable a user of administrativecomputing device 130 and/or treasury client computing device 160interacting with graphical user interface 500 to define one or morealert thresholds for a cash handling device, such as treasury servicecash handling device 140. Such alert thresholds may, for instance,include a first alert threshold for identifying when restocking isrequired at a particular cash handling device, a second alert thresholdfor identifying when inspecting is needed at a particular cash handlingdevice, a third alert threshold for indicating when an expected depositand/or exchange transaction has been missed by a particular client,and/or additional alert thresholds.

At step 208, treasury service computing platform 110 may receive one ormore configuration settings (e.g., from administrative computing device130, treasury client computing device 160, and/or one or more othercomputing devices). Such configuration settings may, for example, bereceived via the one or more configuration interfaces provided at step207. Referring to FIG. 2C, at step 209, treasury service computingplatform 110 may send configuration information to treasury service cashhandling device 140 (e.g., based on the one or more configurationsettings received at step 208, to direct and/or otherwise cause treasuryservice cash handling device 140 to implement the one or moreconfiguration settings received at step 208).

At step 210, treasury service cash handling device 140 may receive theconfiguration information from treasury service computing platform 110.For example, at step 210, treasury service cash handling device 140 mayreceive, via a communication interface (e.g., communication interface148), and from at least one banking server (e.g., treasury servicecomputing platform 110), configuration information defining one or moreconfiguration settings for the cash handling device (e.g., treasuryservice cash handling device 140). For instance, the configurationinformation defining one or more configuration settings for the cashhandling device (e.g., treasury service cash handling device 140) maydefine one or more usage limits for treasury service cash handlingdevice 140, one or more alert thresholds for treasury service cashhandling device 140, and/or other configuration settings. Suchconfiguration information may be received by treasury service cashhandling device 140 directly from treasury service computing platform110 and/or may be received via and/or from treasury device supportserver 150. For example, treasury service computing platform 110 may, insome instances, communicate configuration information to treasury devicesupport server 150, and treasury device support server 150 may in turncommunicate configuration information to treasury service cash handlingdevice 140. At step 211, treasury service cash handling device 140 maystore the configuration information received from treasury servicecomputing platform 110. For example, at step 211, treasury service cashhandling device 140 may store the configuration information defining theone or more configuration settings for the cash handling device (e.g.,treasury service cash handling device 140) received from the at leastone banking server (e.g., treasury service computing platform 110).

In addition to receiving and/or storing configuration information,treasury service cash handling device 140 also may receive and/or storeuser profile information, as illustrated in greater detail below. Suchuser profile information may, for instance, be received from treasuryservice computing platform 110 (e.g., directly and/or via treasurydevice support server 150). In addition, the user profile informationmay, for instance, define which treasury clients are authorized to useone or more cash handling devices, one or more usernames and/orpasswords and/or personal identification numbers (“PIN numbers”) to beused by particular organizations and/or particular users associated withsuch organizations (e.g., organization PIN numbers, employee PINnumbers, and/or the like) when logging into the one or more cashhandling devices, language settings and/or accessibility settings forparticular users of the one or more cash handling devices, and/or otheruser settings.

At step 212, treasury service computing platform 110 may provide one ormore user profile interfaces (e.g., to administrative computing device130, treasury client computing device 160, and/or one or more othercomputing devices). For example, at step 212, treasury service computingplatform 110 may generate and/or send (e.g., to administrative computingdevice 130, treasury client computing device 160, and/or one or moreother computing devices) one or more graphical user interfaces that maybe configured to allow a user (e.g., of administrative computing device130, treasury client computing device 160, or another computing device)to define various user profiles and/or other user settings for treasuryservice cash handling device 140 and/or one or more other cash handlingdevices. In providing the one or more user profile interfaces toadministrative computing device 130 and/or treasury client computingdevice 160, treasury service computing platform 110 may cause, control,and/or direct administrative computing device 130 and/or treasury clientcomputing device 160 to display and/or otherwise present a graphicaluser interface similar to graphical user interface 600, which isillustrated in FIG. 6. As seen in FIG. 6, graphical user interface 600may include one or more user interface controls and/or other elementsthat may enable a user of administrative computing device 130 and/ortreasury client computing device 160 interacting with graphical userinterface 600 to define one or more user profiles for one or moreauthorized users of treasury service cash handling device 140 and/or oneor more other cash handling devices. Such user profiles may, forinstance, be associated with a first treasury client of a financialinstitution operating treasury service computing platform 110, and insome instances, user profiles associated with a second treasury clientdifferent from the first treasury client may be defined on a differentscreen. For example, in providing the one or more user profileinterfaces to administrative computing device 130 and/or treasury clientcomputing device 160, treasury service computing platform 110 mayadditionally or alternatively cause, control, and/or directadministrative computing device 130 and/or treasury client computingdevice 160 to display and/or otherwise present a graphical userinterface similar to graphical user interface 700, which is illustratedin FIG. 7. As seen in FIG. 7, graphical user interface 700 may includeone or more user interface controls and/or other elements that mayenable a user of administrative computing device 130 and/or treasuryclient computing device 160 interacting with graphical user interface700 to define one or more user profiles for one or more authorized usersof treasury service cash handling device 140 and/or one or more othercash handling devices, and such user profiles may be associated with thesecond treasury client different from the first treasury client.

Referring to FIG. 2D, at step 213, treasury service computing platform110 may receive one or more user profile settings (e.g., fromadministrative computing device 130, treasury client computing device160, and/or one or more other computing devices). Such user profilesettings may, for example, be received via the one or more user profileinterfaces provided at step 212. At step 214, treasury service computingplatform 110 may send user profile information to treasury service cashhandling device 140 (e.g., based on the one or more user profilesettings received at step 213, to direct and/or otherwise cause treasuryservice cash handling device 140 to implement the one or more userprofile settings received at step 213).

At step 215, treasury service cash handling device 140 may receive theuser profile information from treasury service computing platform 110.For example, at step 215, treasury service cash handling device 140 mayreceive, via the communication interface (e.g., communication interface148), and from the at least one banking server (e.g., treasury servicecomputing platform 110), user profile information defining one or moreuser settings for the cash handling device. Such user profileinformation may be received by treasury service cash handling device 140directly from treasury service computing platform 110 and/or may bereceived via and/or from treasury device support server 150. Forexample, treasury service computing platform 110 may, in some instances,communicate user profile information to treasury device support server150, and treasury device support server 150 may in turn communicate userprofile information to treasury service cash handling device 140. Atstep 216, treasury service cash handling device 140 may store the userprofile information received from treasury service computing platform110. For example, at step 216, treasury service cash handling device 140may store the user profile information defining the one or more usersettings for the cash handling device (e.g., treasury service cashhandling device 140) received from the at least one banking server(e.g., treasury service computing platform 110). In some instances, oneor more user profile settings may be defined directly on treasuryservice cash handling device 140 via one or more user interfacespresented by treasury service cash handling device 140 instead of and/orin addition to being defined via one or more interfaces provided bytreasury service computing platform 110.

After treasury service cash handling device 140 has been initiated andvarious settings have been defined, treasury service cash handlingdevice 140 may, for example, begin normal operations, in which treasuryservice cash handling device 140 may, for instance, authenticate one ormore users and/or perform one or more transactions, as illustrated ingreater detail below. For example, treasury service cash handling device140 may perform one or more treasury deposit transactions in whichtreasury service cash handling device 140 may accept bulk notes, coins,and/or checks; scan, sort, accept, and/or reject various notes, coins,checks, and/or other items that may be received for deposit; record thequantity of various denominations received, the times at which depositsare made, the users that made such deposits, the destination accountsfor such deposits, whether any items were rejected and/or the like.Additionally or alternatively, treasury service cash handling device 140may enforce one or more deposit limits and/or other limits, prompt auser through a process to handle rejected items, provide one or morereceipts, and/or perform one or more other functions, as illustrated ingreater detail below.

Referring to FIG. 2E, at step 217, treasury service cash handling device140 may present a login interface. For example, at step 217, treasuryservice cash handling device 140 may display and/or otherwise present alogin interface while operating in a standby mode, for instance, whilewaiting for a user to approach and/or request to use treasury servicecash handling device 140 to perform one or more transactions. At step218, treasury service cash handling device 140 may receive a treasuryclient identifier. For example, at step 218, treasury service cashhandling device 140 may receive user input that includes a treasuryclient identifier associated with a particular entity (which may, e.g.,be an organization having one or more users who are authorized to usetreasury service cash handling device 140). At step 219, treasuryservice cash handling device 140 may validate the treasury clientidentifier (e.g., based on configuration information, user profileinformation, and/or the like). At step 220, treasury service cashhandling device 140 may prompt the user of treasury service cashhandling device 140 to enter a user identifier.

Referring to FIG. 2F, at step 221, treasury service cash handling device140 may receive a user identifier. For example, at step 221, treasuryservice cash handling device 140 may receive user input that includes auser identifier associated with a particular user (who may, e.g., beemployed by and/or otherwise affiliated with the organizationcorresponding to the treasury client identifier validated by treasuryservice cash handling device 140 at step 219). At step 222, treasuryservice cash handling device 140 may validate the user identifierreceived at step 221 (e.g., based on user profile information and/orother information). For example, at step 222, treasury service cashhandling device 140 may authenticate the first user of the cash handlingdevice (e.g., treasury service cash handling device 140) based on theuser profile information defining the one or more user settings for thecash handling device (e.g., treasury service cash handling device 140)received from the at least one banking server (e.g., treasury servicecomputing platform 110). In some instances, the user may beauthenticated by treasury service cash handling device 140 based on aclient identifier and a user identifier entered by the user, while inother instances, the user may additionally or alternatively beauthenticated by treasury service cash handling device 140 based ontreasury service cash handling device 140 scanning and/or extractinginformation from a data bearing token, such as a card with a magneticstripe, a radio frequency identification (RFID) tag, and/or the like.

At step 223, treasury service cash handling device 140 may receive adeposit transaction request. For example, at step 223, treasury servicecash handling device 140 may receive, from a first user of the cashhandling device (e.g., treasury service cash handling device 140), arequest to perform a deposit transaction at a deployment location of thecash handling device (e.g., treasury service cash handling device 140).Such a request may, for instance, correspond to and/or include userinput received by treasury service cash handling device 140 via a userinterface displayed and/or otherwise presented by treasury service cashhandling device 140.

In some embodiments, the deployment location of the cash handling devicemay be a retail banking center operated by a financial institution. Forexample, the deployment location of the cash handling device (e.g.,treasury service cash handling device 140) may be a retail bankingcenter operated by a financial institution (which may, e.g., operatetreasury service cash handling device 140 and/or treasury servicecomputing platform 110). In some embodiments, the deployment location ofthe cash handling device may be a shopping mall in which a plurality ofretailers operate retail stores. For example, the deployment location ofthe cash handling device (e.g., treasury service cash handling device140) may be a shopping mall in which a plurality of retailers operateretail stores (and which might not, e.g., be associated with thefinancial institution operating treasury service cash handling device140 and/or treasury service computing platform 110).

At step 224, treasury service cash handling device 140 may present oneor more deposit user interfaces. For example, at step 224, treasuryservice cash handling device 140 may display and/or otherwise presentone or more user interfaces prompting the user of treasury service cashhandling device 140 to insert one or more bills, coins, checks, and/orother items for deposit.

Referring to FIG. 2G, at step 225, treasury service cash handling device140 may receive one or more deposit items. For example, at step 225,based on receiving the request to perform the deposit transaction at thedeployment location of the cash handling device (e.g., treasury servicecash handling device 140), treasury service cash handling device 140 mayreceive, via the item accepting device (e.g., item accepting device145), at least one deposit item for deposit at the deployment locationof the cash handling device (e.g., treasury service cash handling device140).

In some embodiments, the at least one deposit item received for depositmay include one or more currency notes. For example, the at least onedeposit item received for deposit by treasury service cash handlingdevice 140 at step 225 may include one or more currency notes.Additionally or alternatively, the at least one deposit item receivedfor deposit may include one or more currency coins. For example, the atleast one deposit item received for deposit by treasury service cashhandling device 140 at step 225 may include one or more currency coins.Additionally or alternatively, the at least one deposit item receivedfor deposit may include one or more checks. For example, the at leastone deposit item received for deposit by treasury service cash handlingdevice 140 at step 225 may include one or more checks.

At step 226, treasury service cash handling device 140 may validate theone or more deposit items. For example, at step 226, treasury servicecash handling device 140 may validate the at least one deposit itemreceived for deposit at the deployment location of the cash handlingdevice (e.g., treasury service cash handling device 140). For example,in validating the one or more deposit items at step 226, treasuryservice cash handling device 140 may scan and/or sort the one or moreitems received for deposit, accept and/or physically store one or moreitems that are deemed to be valid bills and/or coins and/or otherwiseacceptable items, reject and/or physically return one or more items thatare deemed to be invalid bills and/or coins and/or otherwiseunacceptable items, present one or more graphical user interfaces havinginformation about the deposit transaction (e.g., identifying items thatwere accepted and/or rejected, informing the user why one or more itemswere rejected, prompting the user through a process for re-depositingrejected items, informing the user about deposit limits and/or otherusage limits, and/or the like).

In some embodiments, validating the at least one deposit item receivedfor deposit at the deployment location of the cash handling device mayinclude: scanning, by the internal currency scanning system, one or moredeposit items received for deposit; sorting, by the internal currencytransport system, the one or more deposit items received for deposit;and physically storing, by the internal currency transport system, inthe one or more currency storage cartridges, the one or more deposititems received for deposit. For example, in validating the at least onedeposit item received for deposit at the deployment location of the cashhandling device (e.g., treasury service cash handling device 140),treasury service cash handling device 140 may scan, by the internalcurrency scanning system (e.g., currency scanning system 147 a), one ormore deposit items received for deposit. In addition, treasury servicecash handling device 140 may store, by the internal currency transportsystem (e.g., currency transport system 147 b), the one or more deposititems received for deposit. In addition, treasury service cash handlingdevice 140 may physically store, by the internal currency transportsystem (e.g., currency transport system 147 b), in the one or morecurrency storage cartridges (e.g., storage cartridges 147 c), the one ormore deposit items received for deposit.

In some embodiments, configuration information stored by the cashhandling device may define one or more usage limits, and validating theat least one deposit item received for deposit at the deploymentlocation of the cash handling device may include enforcing the one ormore usage limits defined by the configuration information stored by thecash handling device. For example, configuration information stored bythe cash handling device (e.g., treasury service cash handling device140) may define one or more usage limits, and in validating the at leastone deposit item received for deposit at the deployment location of thecash handling device (e.g., treasury service cash handling device 140),treasury service cash handling device 140 may enforce the one or moreusage limits defined by the configuration information stored by the cashhandling device (e.g., treasury service cash handling device 140). Suchusage limits may be defined by a financial institution operatingtreasury service cash handling device 140 and/or treasury servicecomputing platform 110 and/or may be defined by a client of thefinancial institution operating treasury service cash handling device140 and/or treasury service computing platform 110. In some instances,such usage limits may, for instance, include a maximum deposit limitdefining a maximum amount of currency that can be deposited by one userof treasury service cash handling device 140 and/or in one transaction.

In some embodiments, configuration information stored by the cashhandling device may define one or more alert thresholds, and validatingthe at least one deposit item received for deposit at the deploymentlocation of the cash handling device may include generating at least onedeposit alert based on the one or more alert thresholds defined by theconfiguration information stored by the cash handling device. Forexample, configuration information stored by the cash handling device(e.g., treasury service cash handling device 140) may define one or morealert thresholds, and in validating the at least one deposit itemreceived for deposit at the deployment location of the cash handlingdevice (e.g., treasury service cash handling device 140), treasuryservice cash handling device 140 may generate at least one deposit alertbased on the one or more alert thresholds defined by the configurationinformation stored by the cash handling device (e.g., treasury servicecash handling device 140). Such an alert may, for instance, be sent(e.g., by treasury service cash handling device 140, treasury devicesupport server 150, treasury service computing platform 110) to atreasury client and/or a device associated with the treasury client(e.g., treasury client computing device 160) to notify the treasuryclient of the deposit transaction being performed.

At step 227, treasury service cash handling device 140 may store depositinformation. For example, at step 227, treasury service cash handlingdevice 140 may store deposit information to record the quantities ofitems received in connection with the deposit transaction, thedenominations of the items received, the time at which such items werereceived, the user that performed the deposit transaction, detailsassociated with any items that were rejected, and/or other informationassociated with the deposit transaction. At step 228, treasury servicecash handling device 140 may provide a receipt. For example, at step228, based on validating the at least one deposit item received fordeposit at the deployment location of the cash handling device (e.g.,treasury service cash handling device 140), treasury service cashhandling device 140 may provide a deposit receipt associated with therequest to perform the deposit transaction. In providing such a depositreceipt, treasury service cash handling device 140 may print, dispense,and/or otherwise physically output a receipt for collection by the user,and such a receipt may include information associated with the deposittransaction. For example, the deposit receipt may include any and/or allof the deposit information stored by treasury service cash handlingdevice 140 at step 227.

After treasury service cash handling device 140 has received and/orvalidated one or more deposit items in connection with performing adeposit transaction, treasury service cash handling device 140 mayupdate treasury service computing platform 110, treasury device supportserver 150, and/or one or more other servers. For example, treasuryservice cash handling device 140 may send commands and/or otherinformation to treasury service computing platform 110 and/or treasurydevice support server 150 to cause treasury service computing platform110 and/or treasury device support server 150 to credit one or moreaccounts for the items deposited at treasury service cash handlingdevice 140, generate and/or send one or more alerts based on the deposittransaction being performed, generate and/or send one or more reportsbased on the deposit transaction being performed, evaluate restockingand/or transport needs at treasury service cash handling device 140,and/or perform other functions, as illustrated in greater detail below.

Referring to FIG. 2H, at step 229, treasury service cash handling device140 may generate a deposit transaction record. For example, at step 229,based on validating the at least one deposit item received for depositat the deployment location of the cash handling device (e.g., treasuryservice cash handling device 140), treasury service cash handling device140 may generate a deposit transaction record associated with therequest to perform the deposit transaction, the deposit transactionrecord comprising deposit information directing at least one bankingserver (e.g., treasury service computing platform 110) to apply aprovisional credit to at least one treasury account associated with thefirst user of the cash handling device (e.g., treasury service cashhandling device 140). For instance, treasury service cash handlingdevice 140 may generate the deposit transaction record to direct and/orotherwise cause treasury service computing platform 110 to credit theappropriate client for the deposit received by treasury service cashhandling device 140, and the credit may be provisional in nature as itmay be subject to verification (e.g., by the financial institutionoperating treasury service cash handling device 140 and/or treasuryservice computing platform 110) before being confirmed, reconciled, andmade non-provisional, as illustrated in greater detail below.Additionally or alternatively, the deposit transaction record generatedby treasury service cash handling device 140 at step 229 may includesome or all of the deposit information stored by treasury service cashhandling device 140 at step 227 (e.g., based on the configurationsettings for treasury service cash handling device 140 and/or otherdeployment parameters).

In some embodiments, the deposit information may direct the at least onebanking server to credit the at least one treasury account associatedwith the first user of the cash handling device with an amount of fundsassociated with the at least one deposit item received for deposit atthe deployment location of the cash handling device and validated by thecash handling device. For example, the deposit information (which may,e.g., be included in the deposit transaction record generated bytreasury service cash handling device 140 at step 229) may direct the atleast one banking server (e.g., treasury service computing platform 110)to credit the at least one treasury account associated with the firstuser of the cash handling device (e.g., treasury service cash handlingdevice 140) with an amount of funds associated with the at least onedeposit item received for deposit at the deployment location of the cashhandling device (e.g., treasury service cash handling device 140) andvalidated by the cash handling device (e.g., treasury service cashhandling device 140). For instance, if treasury service cash handlingdevice 140 received $400 in deposit items and accepted and validated$370 of the deposit items (e.g., and rejected the other $30 of thedeposit items), then treasury service cash handling device 140 maygenerate a deposit transaction record having deposit informationdirecting treasury service computing platform 110 to credit an accountassociated with the depositor in the amount of $370. As noted above, theaccount may be a treasury account maintained by the financialinstitution for a small business, retailer, or other organization, andthe deposit may be made by an employee or other affiliate of theorganization. In addition, treasury service cash handling device 140and/or one or more other cash handling devices may be deployed by thefinancial institution solely for use by such treasury clients (e.g.,organizational clients) and might not be usable by retail clients (e.g.,personal or individual clients) of the financial institution, forinstance.

In some embodiments, the deposit transaction record may includeinformation identifying one or more denominations of currency receivedby the cash handling device, one or more quantities of specificdenominations of currency received by the cash handling device, a timeat which the deposit transaction was completed, a user that performedthe deposit transaction, a quantity of deposit items rejected, and oneor more destination accounts into which currency was deposited. Forexample, the deposit transaction record (which may, e.g., be generatedby treasury service cash handling device 140 at step 229) may includeinformation identifying one or more denominations of currency receivedby the cash handling device (e.g., treasury service cash handling device140), one or more quantities of specific denominations of currencyreceived by the cash handling device (e.g., treasury service cashhandling device 140), a time at which the deposit transaction wascompleted, a user that performed the deposit transaction, a quantity ofdeposit items rejected, and one or more destination accounts into whichcurrency was deposited. An example of the information that may beincluded in a deposit transaction record generated by treasury servicecash handling device 140 is illustrated in the following table:

TABLE A Deposit Transaction Record Unique Record Identifier NumberAAAAAA Unique Cash Handling Device Identifier BBBBBB Quantity ofCurrency Received 275 notes, 400 coins Denominations Received $100, $50,$20, $1, $0.25 Quantities of Denominations Received 25 × $100, 25 × $50,25 × $20, 200 × $1, 400 × $0.25 Time of Completion March 19, 2016, at2:00 PM ET User Performing Transaction First M. Last Quantity of ItemsRejected 3 notes Destination Account(s) Treasury Client Account 1

At step 230, treasury service cash handling device 140 may send thedeposit transaction record to treasury service computing platform 110.For example, at step 230, treasury service cash handling device 140 maysend, via the communication interface (e.g., communication interface148), and to the at least one banking server (e.g., treasury servicecomputing platform 110), the deposit transaction record. Treasuryservice cash handling device 140 may, for instance, send the deposittransaction record to treasury service computing platform 110 tofacilitate the crediting of one or more accounts in connection with thedeposit, to facilitate the generation of one or more alerts,notifications, and/or reports, and/or to facilitate inventory monitoringand/or restocking of treasury service cash handling device 140. In someinstances, in sending the deposit transaction record to treasury servicecomputing platform 110, treasury service cash handling device 140 maysend the deposit transaction record directly to treasury servicecomputing platform 110 (e.g., via a connection established betweentreasury service computing platform 110 and treasury service cashhandling device 140), while in other instances, in sending the deposittransaction record to treasury service computing platform 110, treasuryservice cash handling device 140 may send the deposit transaction recordto treasury service computing platform 110 via treasury device supportserver 150. For instance, treasury service cash handling device 140 maysend the deposit transaction record to treasury device support server150, which in turn may send the deposit transaction record to treasuryservice computing platform 110.

After performing one transaction, such as the deposit transactionillustrated above, treasury service cash handling device 140 may performanother transaction, such as a change order transaction, for example, asillustrated in greater detail below. In performing such a change ordertransaction, treasury service cash handling device 140 may, forinstance, authenticate a user, accept bulk notes and/or coins; scan,sort, accept, and/or reject various notes, coins, checks, and/or otheritems that may be received for exchange; receive input requestingspecific quantities and/or denominations of notes and/or coins intowhich inserted currency should be exchanged; calculate specificquantities and/or denominations of notes and/or coins into whichinserted currency should be exchanged to ensure an even exchange;dispense one or more bills and/or rolled coins (e.g., wrapped rolls ofcoins of particular denominations); record the quantity of variousdenominations received, the time at which the exchange is made, the userthat made the exchange, any accounts involved, whether any items wererejected and/or the like. Additionally or alternatively, treasuryservice cash handling device 140 may enforce one or more usage limitsand/or other limits, prompt a user through a process to handle rejecteditems, provide one or more receipts, and/or perform one or more otherfunctions, as illustrated in greater detail below.

At step 231, treasury service cash handling device 140 may present alogin interface. For example, at step 231, treasury service cashhandling device 140 may display and/or otherwise present a logininterface while operating in a standby mode, for instance, while waitingfor a user to approach and/or request to use treasury service cashhandling device 140 to perform one or more transactions. In someinstances, treasury service cash handling device 140 may skip one ormore user authentication steps if the previous user of treasury servicecash handling device 140 is still authenticated and wishes to performanother transaction, while in other instances, treasury service cashhandling device 140 may return to the login interface after eachtransaction is completed as a default security measure.

At step 232, treasury service cash handling device 140 may receive atreasury client identifier. For example, at step 232, treasury servicecash handling device 140 may receive user input that includes a treasuryclient identifier associated with a particular entity (which may, e.g.,be an organization having one or more users who are authorized to usetreasury service cash handling device 140). Referring to FIG. 2I, atstep 233, treasury service cash handling device 140 may validate thetreasury client identifier (e.g., based on configuration information,user profile information, and/or the like). At step 234, treasuryservice cash handling device 140 may prompt the user of treasury servicecash handling device 140 to enter a user identifier.

At step 235, treasury service cash handling device 140 may receive auser identifier. For example, at step 235, treasury service cashhandling device 140 may receive user input that includes a useridentifier associated with a particular user (who may, e.g., be employedby and/or otherwise affiliated with the organization corresponding tothe treasury client identifier validated by treasury service cashhandling device 140 at step 233). At step 236, treasury service cashhandling device 140 may validate the user identifier received at step235 (e.g., based on user profile information and/or other information).For example, at step 236, treasury service cash handling device 140 mayauthenticate the second user of the cash handling device (e.g., treasuryservice cash handling device 140) based on the user profile informationdefining the one or more user settings for the cash handling device(e.g., treasury service cash handling device 140) received from the atleast one banking server (e.g., treasury service computing platform110). In some instances, the user may be authenticated by treasuryservice cash handling device 140 based on a client identifier and a useridentifier entered by the user, while in other instances, the user mayadditionally or alternatively be authenticated by treasury service cashhandling device 140 based on treasury service cash handling device 140scanning and/or extracting information from a data bearing token, suchas a card with a magnetic stripe, a radio frequency identification(RFID) tag, and/or the like.

Referring to FIG. 2J, at step 237, treasury service cash handling device140 may receive a change order transaction request. For example, at step237, treasury service cash handling device 140 may receive, from asecond user of the cash handling device (e.g., treasury service cashhandling device 140), a request to perform a change order transaction atthe deployment location of the cash handling device (e.g., treasuryservice cash handling device 140). Such a request may, for instance,correspond to and/or include user input received by treasury servicecash handling device 140 via a user interface displayed and/or otherwisepresented by treasury service cash handling device 140. At step 238,treasury service cash handling device 140 may present one or more changeorder user interfaces. For example, at step 238, treasury service cashhandling device 140 may display and/or otherwise present one or moreuser interfaces prompting the user of treasury service cash handlingdevice 140 to insert one or more bills and/or coins to be exchanged,indicate what specific denominations/quantities into which the inserteditems should be changed, and/or the like.

At step 239, treasury service cash handling device 140 may receive oneor more exchange items. For example, at step 239, based on receiving therequest to perform the change order transaction at the deploymentlocation of the cash handling device (e.g., treasury service cashhandling device 140), treasury service cash handling device 140 mayreceive, via the item accepting device (e.g., item accepting device145), at least one change order item for exchange at the deploymentlocation of the cash handling device (e.g., treasury service cashhandling device 140).

In some embodiments, the at least one change order item received forexchange may include one or more currency notes. For example, the atleast one change order item received for exchange by treasury servicecash handling device 140 at step 239 may include one or more currencynotes. In some embodiments, the at least one change order item receivedfor exchange may include one or more currency coins. For example, the atleast one change order item received for exchange by treasury servicecash handling device 140 at step 239 may include one or more currencycoins.

At step 240, treasury service cash handling device 140 may validate theone or more change order items for exchange (which may, e.g., also bereferred to as “exchange items”). For example, at step 240, treasuryservice cash handling device 140 may validate the at least one changeorder item received for exchange at the deployment location of the cashhandling device (e.g., treasury service cash handling device 140). Forexample, in validating the one or more exchange items at step 240,treasury service cash handling device 140 may scan and/or sort the oneor more items received for exchange, accept and/or physically store oneor more items that are deemed to be valid bills and/or coins and/orotherwise acceptable items, reject and/or physically return one or moreitems that are deemed to be invalid bills and/or coins and/or otherwiseunacceptable items, present one or more graphical user interfaces havinginformation about the exchange transaction (e.g., identifying items thatwere accepted and/or rejected, informing the user why one or more itemswere rejected, prompting the user through a process for re-depositingrejected items, informing the user about exchange limits and/or otherusage limits, and/or the like).

In some embodiments, validating the at least one change order itemreceived for exchange at the deployment location of the cash handlingdevice may include: scanning, by the internal currency scanning system,one or more change order items received for exchange; sorting, by theinternal currency transport system, the one or more change order itemsreceived for exchange; and physically storing, by the internal currencytransport system, in the one or more currency storage cartridges, theone or more change order items received for exchange. For example, invalidating the at least one change order item received for exchange atthe deployment location of the cash handling device (e.g., treasuryservice cash handling device 140), treasury service cash handling device140 may scan, by the internal currency scanning system (e.g., currencyscanning system 147 a), one or more change order items received forexchange. In addition, treasury service cash handling device 140 maysort, by the internal currency transport system (e.g., currencytransport system 147 b), the one or more change order items received forexchange. In addition, treasury service cash handling device 140 mayphysically store, by the internal currency transport system (e.g.,currency transport system 147 b), in the one or more currency storagecartridges (e.g., storage cartridges 147 c), the one or more changeorder items received for exchange. In some instances, items received forexchange and items received for deposit may be separately stored andmaintained by treasury service cash handling device 140 in differentstorage cartridges (e.g., storage cartridges 147 c), while in otherinstances, deposit items and exchange items may be commingled.

In some embodiments, configuration information stored by the cashhandling device may define one or more usage limits, and validating theat least one change order item received for exchange at the deploymentlocation of the cash handling device may include enforcing the one ormore usage limits defined by the configuration information stored by thecash handling device. For example, configuration information stored bythe cash handling device (e.g., treasury service cash handling device140) may define one or more usage limits, and in validating the at leastone change order item received for exchange at the deployment locationof the cash handling device (e.g., treasury service cash handling device140), treasury service cash handling device 140 may enforce the one ormore usage limits defined by the configuration information stored by thecash handling device (e.g., treasury service cash handling device 140).Such usage limits may be defined by a financial institution operatingtreasury service cash handling device 140 and/or treasury servicecomputing platform 110 and/or may be defined by a client of thefinancial institution operating treasury service cash handling device140 and/or treasury service computing platform 110. In some instances,such usage limits may, for instance, include a maximum exchange limitdefining a maximum amount of currency that can be exchanged by one userof treasury service cash handling device 140 and/or in one transaction.

In some embodiments, configuration information stored by the cashhandling device may define one or more alert thresholds, and validatingthe at least one change order item received for exchange at thedeployment location of the cash handling device may include generatingat least one exchange alert based on the one or more alert thresholdsdefined by the configuration information stored by the cash handlingdevice. For example, configuration information stored by the cashhandling device (e.g., treasury service cash handling device 140) maydefine one or more alert thresholds, and in validating the at least onechange order item received for exchange at the deployment location ofthe cash handling device (e.g., treasury service cash handling device140), treasury service cash handling device 140 may generate at leastone exchange alert based on the one or more alert thresholds defined bythe configuration information stored by the cash handling device (e.g.,treasury service cash handling device 140). Such an alert may, forinstance, be sent (e.g., by treasury service cash handling device 140,treasury device support server 150, treasury service computing platform110) to a treasury client and/or a device associated with the treasuryclient (e.g., treasury client computing device 160) to notify thetreasury client of the exchange transaction being performed.

Referring to FIG. 2K, at step 241, treasury service cash handling device140 may dispense currency. For example, at step 241, based on validatingthe at least one change order item received for exchange at thedeployment location of the cash handling device (e.g., treasury servicecash handling device 140), treasury service cash handling device 140 maydispense, via the item dispensing device (e.g., item dispensing device146), one or more currency items to complete the change ordertransaction. In dispensing one or more currency items, treasury servicecash handling device 140 may, for example, dispense one or more billsand/or notes, rolls of coins (which may also be referred to as “rolledcoin”), and/or other items, in accordance with the denominations and/orquantities requested by the user of treasury service cash handlingdevice 140 and/or determined by treasury service cash handling device140 itself (e.g., to ensure an even exchange of funds).

At step 242, treasury service cash handling device 140 may storeexchange information. For example, at step 242, treasury service cashhandling device 140 may store exchange information to record thequantities of items received in connection with the exchangetransaction, the denominations of the items received, the time at whichsuch items were received, the user that performed the deposittransaction, details associated with any items that were rejected,and/or other information associated with the exchange transaction. Atstep 243, treasury service cash handling device 140 may provide areceipt. For example, based on validating the at least one change orderitem received for exchange at the deployment location of the cashhandling device (e.g., treasury service cash handling device 140),treasury service cash handling device 140 may provide an exchangereceipt associated with the request to perform the change ordertransaction. In providing such an exchange receipt, treasury servicecash handling device 140 may print, dispense, and/or otherwisephysically output a receipt for collection by the user, and such areceipt may include information associated with the exchangetransaction. For example, the exchange receipt may include any and/orall of the exchange information stored by treasury service cash handlingdevice 140 at step 242.

After treasury service cash handling device 140 has received and/orvalidated one or more exchange items and dispensed one or more currencyitems in connection with performing an exchange transaction, treasuryservice cash handling device 140 may update treasury service computingplatform 110, treasury device support server 150, and/or one or moreother servers. For example, treasury service cash handling device 140may send commands and/or other information to treasury service computingplatform 110 and/or treasury device support server 150 to cause treasuryservice computing platform 110 and/or treasury device support server 150to update one or more transaction history records to reflect the itemsexchanged at treasury service cash handling device 140, generate and/orsend one or more alerts based on the exchange transaction beingperformed, generate and/or send one or more reports based on theexchange transaction being performed, evaluate restocking and/ortransport needs at treasury service cash handling device 140, and/orperform other functions, as illustrated in greater detail below.

At step 244, treasury service cash handling device 140 may generate anexchange transaction record. For example, at step 244, treasury servicecash handling device 140 may generate a change order transaction recordassociated with the request to perform the change order transaction, thechange order transaction record comprising change order informationdirecting the at least one banking server (e.g., treasury servicecomputing platform 110) to update one or more transaction historyrecords associated with the second user of the cash handling device(e.g., treasury service cash handling device 140). For instance,treasury service cash handling device 140 may generate the exchangetransaction record to direct and/or otherwise cause treasury servicecomputing platform 110 to update various records, including accounthistory and/or transaction history records, maintained by treasuryservice computing platform 110 to reflect the exchange transaction beingperformed by treasury service cash handling device 140. Additionally oralternatively, the exchange transaction record generated by treasuryservice cash handling device 140 at step 244 may include some or all ofthe exchange information stored by treasury service cash handling device140 at step 242 (e.g., based on the configuration settings for treasuryservice cash handling device 140 and/or other deployment parameters).

Referring to FIG. 2L, at step 245, treasury service cash handling device140 may send the exchange transaction record to treasury servicecomputing platform 110. For example, at step 245, treasury service cashhandling device 140 may send, via the communication interface (e.g.,communication interface 148), and to the at least one banking server(e.g., treasury service computing platform 110), the change ordertransaction record. Treasury service cash handling device 140 may, forinstance, send the change order transaction record (which may, e.g.,also be referred to as an “exchange transaction record”) to treasuryservice computing platform 110 to facilitate the updating of one or moreaccount history records in connection with the exchange, to facilitatethe generation of one or more alerts, notifications, and/or reports,and/or to facilitate inventory monitoring and/or restocking of treasuryservice cash handling device 140. In some instances, in sending theexchange transaction record to treasury service computing platform 110,treasury service cash handling device 140 may send the exchangetransaction record directly to treasury service computing platform 110(e.g., via a connection established between treasury service computingplatform 110 and treasury service cash handling device 140), while inother instances, in sending the exchange transaction record to treasuryservice computing platform 110, treasury service cash handling device140 may send the exchange transaction record to treasury servicecomputing platform 110 via treasury device support server 150. Forinstance, treasury service cash handling device 140 may send theexchange transaction record to treasury device support server 150, whichin turn may send the exchange transaction record to treasury servicecomputing platform 110.

After sending the exchange transaction record to treasury servicecomputing platform 110, treasury service cash handling device 140 mayrepeat one or more steps of the example event sequence discussed above,for instance, to perform additional deposit transactions and/or changeorder transactions. Additionally or alternatively, treasury service cashhandling device 140 may perform other transactions, such as withdrawaltransactions, inquiry transactions, and/or other transactions. Inaddition to performing one or more additional transactions, treasuryservice cash handling device 140 also may perform a refill process(which may, e.g., also be referred to as a “restocking process”) inwhich treasury service cash handling device 140 may authenticate a userassociated with a transport carrier company, receive a refill, and/orupdate one or more counts and/or other records, among other things, asillustrated in greater detail below.

At step 246, treasury service cash handling device 140 may present alogin interface. At step 247, treasury service cash handling device 140may receive a transport carrier identifier. For example, at step 247,treasury service cash handling device 140 may receive user input thatincludes a transport carrier identifier associated with a transportcompany and/or an authorized user associated with such a transportcompany (which may, e.g., be an organization with which a financialinstitution operating treasury service cash handling device 140 and/ortreasury service computing platform 110 has contracted to physicallyvisit, load, unload, and/or refill one or more cash handling deviceswith currency and/or other items). At step 248, treasury service cashhandling device 140 may validate the transport carrier identifierreceived at step 247.

Referring to FIG. 2M, at step 249, treasury service cash handling device140 may receive one or more restocking items. For example, at step 249,treasury service cash handling device 140 may receive one or morerefilled cartridges having currency notes, rolls of coins, and/or thelike. Such restocking items may, for instance, be processed and/ororganized by the internal storage and transport systems of treasuryservice cash handling device 140 (which may, e.g., utilize one or morerollers, belts, cartridges, and/or other components to organize and/orstore currency within treasury service cash handling device 140 and/orfor use by treasury service cash handling device 140). At step 250,treasury service cash handling device 140 may update one or moreinternal inventory counts. At step 251, treasury service cash handlingdevice 140 may store updated inventory information.

FIGS. 3A-3H depict another illustrative event sequence for utilizingcash handling devices to provide treasury functions and implementing acomputing platform to control a plurality of cash handling devices inaccordance with one or more example embodiments. As discussed in greaterdetail below, the event sequence shown in FIGS. 3A-3H illustrates, amongother things, how a server, such as treasury service computing platform110, may receive aggregated activity information from various cashhandling devices, process deposit transactions, generate alerts forclients, transport companies, and/or other entities, monitor currencylevels at various cash handling devices, provide portal interfacesand/or reports to client devices, and/or perform other functions.

Referring to FIG. 3A, at step 301, treasury service computing platform110 may receive activity information (e.g., from treasury service cashhandling device 140, from one or more other cash handling devices, fromtreasury device support server 150, from one or more other servers ordevices). For example, at step 301, treasury service computing platform110 may receive, via the communication interface (e.g., communicationinterface 115), and from one or more cash handling devices (e.g.,treasury service cash handling device 140), aggregated activityinformation comprising a plurality of transaction records. For instance,treasury service computing platform 110 may receive transaction recordsidentifying each transaction performed at treasury service cash handlingdevice 140, which user performed the particular transaction, the amountof funds involved in the particular transaction, the type of theparticular transaction (e.g., deposit, change order, withdrawal, and/orthe like), the time the particular transaction was performed, themachine on which the particular transaction was performed, and/or otherinformation. The aggregated activity information received by treasuryservice computing platform 110 at step 301 may include transactionsrecords from treasury service cash handling device 140 and/or one ormore other cash handling devices, which may be located at one or moredifferent locations than the location at which treasury service cashhandling device 140 is located. In some instances, treasury servicecomputing platform 110 may receive aggregated activity informationdirectly from treasury service cash handling device 140 and/or one ormore other cash handling devices, while in other instances, treasuryservice computing platform 110 may receive the aggregated activityinformation from treasury device support server 150 (which may, e.g.,receive and/or aggregate activity information from a plurality of cashhandling devices, including treasury service cash handling device 140).

In some embodiments, the plurality of transaction records received fromthe one or more cash handling devices may include informationidentifying, for each transaction, a specific user who performed thetransaction, an amount of currency involved in the transaction, a timeat which the transaction occurred, and a specific cash handling deviceon which the transaction was performed. For example, the plurality oftransaction records received by treasury service computing platform 110from the one or more cash handling devices (e.g., treasury service cashhandling device 140) may include information identifying, for eachtransaction, a specific user who performed the transaction, an amount ofcurrency involved in the transaction, a time at which the transactionoccurred, and a specific cash handling device on which the transactionwas performed. In some instances, a transaction record may additionallyor alternatively identify the type of transaction that was performed, aswell as other information about the transaction, such as one or moredenominations of currency received by the cash handling device, one ormore quantities of specific denominations of currency received by thecash handling device, a time at which the deposit transaction wascompleted, a user that performed the deposit transaction, a quantity ofdeposit items rejected, and one or more destination accounts into whichcurrency was deposited, as discussed above.

In some embodiments, receiving the aggregated activity information mayinclude: receiving, via the communication interface, and from a firstcash handling device of the one or more cash handling devices, firstactivity information comprising a first plurality of transaction recordsassociated with transactions performed by the first cash handlingdevice; and receiving, via the communication interface, and from asecond cash handling device of the one or more cash handling devices,second activity information comprising a second plurality of transactionrecords associated with transaction performed by the second cashhandling device. For example, in receiving the aggregated activityinformation, treasury service computing platform 110 may receive, viathe communication interface (e.g., communication interface 115), andfrom a first cash handling device of the one or more cash handlingdevices (e.g., treasury service cash handling device 140), firstactivity information comprising a first plurality of transaction recordsassociated with transactions performed by the first cash handlingdevice. In addition, treasury service computing platform 110 mayreceive, via the communication interface (e.g., communication interface115), and from a second cash handling device of the one or more cashhandling devices (e.g., a cash handling device different from treasuryservice cash handling device 140), second activity informationcomprising a second plurality of transaction records associated withtransaction performed by the second cash handling device. In someinstances, the first cash handling device may be located at a firstdeployment location, and the second cash handling device may be locatedat a second deployment location different from the first deploymentlocation. In some instances, the first deployment location may be aretail banking center operated by a financial institution, and thesecond deployment location may be a shopping mall in which a pluralityof retailers operate retail stores.

At step 302, treasury service computing platform 110 may store theactivity information received at step 301. For example, treasury servicecomputing platform 110 may store the aggregated activity information intreasury service database 114. At step 303, treasury service computingplatform 110 may identify one or more deposit transactions (e.g., basedon the activity information received at step 301). For example, at step303, treasury service computing platform 110 may identify one or moredeposit transactions based on the aggregated activity informationcomprising the plurality of transaction records received from the one ormore cash handling devices (e.g., treasury service cash handling device140).

At step 304, treasury service computing platform 110 may generate one ormore account credit commands (e.g., based on identifying the one or moredeposit transactions at step 303). For example, at step 304, based onidentifying the one or more deposit transactions based on the aggregatedactivity information comprising the plurality of transaction recordsreceived from the one or more cash handling devices (e.g., treasuryservice cash handling device 140), treasury service computing platform110 may generate one or more account credit commands, the one or moreaccount credit commands directing at least one account managementcomputer system (e.g., account management computer system 120) to applyone or more provisional credits to one or more treasury accountsassociated with the one or more deposit transactions.

Referring to FIG. 3B, at step 305, treasury service computing platform110 may send the one or more account credit commands to accountmanagement computer system 120. For example, at step 305, treasuryservice computing platform 110 may send, via the communication interface(e.g., communication interface 115), to the at least one accountmanagement computer system (e.g., account management computer system120), the one or more account credit commands directing the at least oneaccount management computer system (e.g., account management computersystem 120) to apply the one or more provisional credits to the one ormore treasury accounts associated with the one or more deposittransactions. For instance, in this way, treasury service computingplatform 110 may control, direct, and/or otherwise cause accountmanagement computer system 120 to provisionally credit correspondingtreasury client accounts maintained by the financial institutionoperating treasury service computing platform 110 and/or treasuryservice cash handling device 140.

At step 306, account management computer system 120 may receive the oneor more account credit commands from treasury service computing platform110. At step 307, account management computer system 120 may apply oneor more provisional credits based on the one or more account creditcommands received from treasury service computing platform 110. Forexample, account management computer system 120 may update one or moreaccount records to provisionally credit one or more specific accountsbased on the account credit commands received from treasury servicecomputing platform 110.

As illustrated in greater detail below, treasury service computingplatform 110 also may generate and/or send various alerts to clientcomputing devices, such as treasury client computing device 160, basedon specific transactions exceeding specific alert thresholds, based onspecific transactions occurring or not occurring, and/or based on otherfactors and/or circumstances. In some instances, treasury servicecomputing platform 110 may generate one or more alerts based on messagesreceived from treasury device support server 150 (e.g., a mid-daymessage indicating that an expected deposit or exchange has not occurredby a particular time, such as an expected deposit from a particularclient by 2:30 pm).

At step 308, treasury service computing platform 110 may generate one ormore client alerts (e.g., based on the activity information received atstep 301). For example, at step 308, treasury service computing platform110 may generate a client alert message based on the aggregated activityinformation comprising the plurality of transaction records receivedfrom the one or more cash handling devices (e.g., treasury service cashhandling device 140).

Referring to FIG. 3C, at step 309, treasury service computing platform110 may send one or more client alerts (e.g., to treasury clientcomputing device 160 and/or to one or more other client computingdevices, based on one or more configuration settings stored by treasuryservice computing platform 110 and/or specific to one or more treasuryclients). For example, at step 309, treasury service computing platform110 may send, via the communication interface (e.g., communicationinterface 115), to a client computing device (e.g., treasury clientcomputing device 160), the client alert message generated based on theaggregated activity information comprising the plurality of transactionrecords received from the one or more cash handling devices (e.g.,treasury service cash handling device 140).

At step 310, treasury service computing platform 110 may generate one ormore internal alerts (e.g., based on the activity information receivedat step 301). For example, at step 310, treasury service computingplatform 110 may generate an internal alert message based on theaggregated activity information comprising the plurality of transactionrecords received from the one or more cash handling devices (e.g.,treasury service cash handling device 140). Such an internal alertmessage may, for instance, include information identifying attempts todeposit more than a permitted maximum amount, information identifyingrejected notes (which may, e.g., have been rejected by treasury servicecash handling device 140 in connection with a particular transaction),and/or information identifying other circumstances and/or issuesexceeding one or more internal alert thresholds.

At step 311, treasury service computing platform 110 may send the one ormore internal alerts (e.g., to administrative computing device 130and/or one or more other computing devices associated with theorganization operating treasury service computing platform 110). Forexample, at step 311, treasury service computing platform 110 may send,via the communication interface (e.g., communication interface 115), toan administrative computing device (e.g., administrative computingdevice 130), the internal alert message generated based on theaggregated activity information comprising the plurality of transactionrecords received from the one or more cash handling devices (e.g.,treasury service cash handling device 140). For instance, treasuryservice computing platform 110 may send such an alert message toadministrative computing device 130 and/or one or more devices internalto the financial institution operating treasury service computingplatform 110 based on one or more configuration settings. For example,different alerts associated with different clients may be directed todifferent financial institution devices and/or users who may supportand/or serve those specific clients.

At step 312, treasury service computing platform 110 may evaluate one ormore currency levels of one or more cash handling devices (e.g.,treasury service cash handling device 140 and/or one or more other cashhandling devices). For example, at step 312, treasury service computingplatform 110 may evaluate a currency level indicative of an amount ofcurrency stored in a first cash handling device of the one or more cashhandling devices (e.g., treasury service cash handling device 140). Forinstance, treasury service computing platform 110 may evaluate currentcurrency levels to identify expected and/or urgent restocking needs, soas to identify, prevent, and/or correct shortfalls in currency inventoryat the one or more cash handling devices (e.g., treasury service cashhandling device 140). Treasury service computing platform 110 may, forinstance, evaluate currency levels for a plurality of cash handlingdevices at various locations, including treasury service cash handlingdevice 140.

Referring to FIG. 3D, at step 313, treasury service computing platform110 may identify one or more restocking needs (e.g., based on evaluatingthe one or more currency levels of the one or more cash handling devicesat step 312). For example, at step 313, treasury service computingplatform 110 may identify a restocking need based on evaluating thecurrency level indicative of the amount of currency stored in the firstcash handling device of the one or more cash handling devices (e.g.,treasury service cash handling device 140). Treasury service computingplatform 110 may identify such a restocking need, for instance, byforecasting usage of treasury service cash handling device 140 andcomparing future/expected currency requirements for treasury servicecash handling device 140 to current currency levels of treasury servicecash handling device 140.

At step 314, treasury service computing platform 110 may generate one ormore restocking requests (e.g., based on identifying the one or morerestocking needs at step 313 for various cash handling devices,including treasury service cash handling device 140). For example, atstep 314, based on identifying the restocking need, treasury servicecomputing platform 110 may generate a restocking request, and therestocking request may direct a transport agent to restock the firstcash handling device of the one or more cash handling devices (e.g.,treasury service cash handling device 140).

At step 315, treasury service computing platform 110 may send the one ormore restocking requests (e.g., to transport carrier computer system 170and/or one or more other transport carrier devices). For example, atstep 315, treasury service computing platform 110 may send, via thecommunication interface (e.g., communication interface 115), to atransport computer system (e.g., transport carrier computer system 170),the restocking request directing the transport agent to restock thefirst cash handling device of the one or more cash handling devices(e.g., treasury service cash handling device 140). For instance,treasury service computing platform 110 may send one or more non-urgent(e.g., scheduled) requests and/or one or more urgent (e.g., unscheduled)requests to transport carrier computer system 170 to restock specificcash handling devices, such as treasury service cash handling device140, so as to direct and/or control one or more armored transportcarrier vehicles and/or a transport carrier company to visit andphysically restock one or more specific cash handling devices, such astreasury service cash handling device 140.

As illustrated in greater detail below, treasury service computingplatform 110 also may provide one or more management interfaces to oneor more administrative devices (e.g., administrative computing device130) and/or administrative users (who may, e.g., be associated with thefinancial institution operating treasury service computing platform 110and/or treasury service cash handling device 140). Such managementinterfaces may, for instance, allow an administrative user to updatevarious settings, including bank-imposed and/or compliance-imposedtransaction limits, alerts, and/or other settings. In addition, treasuryservice computing platform 110 may update one or more cash handlingdevices, such as treasury service cash handling device 140, and/orsupport servers, such as treasury device support server 150, inaccordance with the settings and/or any changes to the settings.

At step 316, treasury service computing platform 110 may receive arequest for one or more administrative interfaces (e.g., fromadministrative computing device 130). For example, at step 316, treasuryservice computing platform 110 may receive, via the communicationinterface (e.g., communication interface 115), from an administrativecomputing device (e.g., administrative computing device 130), a requestfor an administrative portal.

Referring to FIG. 3E, at step 317, treasury service computing platform110 may provide one or more administrative interfaces (e.g., toadministrative computing device 130). For example, at step 317, based onreceiving the request for the administrative portal, treasury servicecomputing platform 110 may provide, via the communication interface(e.g., communication interface), to the administrative computing device(e.g., administrative computing device 130), at least one administrativeinterface.

For example, in providing the one or more administrative interfaces toadministrative computing device 130, treasury service computing platform110 may cause, control, and/or direct administrative computing device130 to display and/or otherwise present a graphical user interfacesimilar to graphical user interface 800, which is illustrated in FIG. 8.As seen in FIG. 8, graphical user interface 800 may include one or moreuser interface controls and/or other elements that may enable a user ofadministrative computing device 130 interacting with graphical userinterface 800 to update various settings, including usage limitsettings, alert threshold settings, and/or other settings, and/or mayenable a user of administrative computing device 130 interacting withgraphical user interface 800 to access a menu providing access toinformation and controls over cash handling device currency levels andrestocking functions. Additionally or alternatively, in providing theone or more administrative interfaces to administrative computing device130, treasury service computing platform 110 may cause, control, and/ordirect administrative computing device 130 to display and/or otherwisepresent a graphical user interface similar to graphical user interface900, which is illustrated in FIG. 9. As seen in FIG. 9, graphical userinterface 900 may include one or more user interface controls and/orother elements that may enable a user of administrative computing device130 interacting with graphical user interface 900 to view currencylevels at various cash handling devices, view and/or edit restockingsettings and alerts, and/or access and/or control other information.

At step 318, treasury service computing platform 110 may receive inputvia the one or more administrative interfaces. For example, at step 318,treasury service computing platform 110 may receive, via thecommunication interface (e.g., communication interface 115), from theadministrative computing device (e.g., administrative computing device130), configuration input defining one or more configuration settingsfor at least one cash handling device of the one or more cash handlingdevices (e.g., treasury service cash handling device 140), and theconfiguration input may have been received by the administrativecomputing device (e.g., administrative computing device 130) via the atleast one administrative interface (which may, e.g., have been providedto administrative computing device 130 by treasury service computingplatform 110 at step 317).

At step 319, treasury service computing platform 110 may store one ormore updated configuration settings for one or more cash handlingdevices (e.g., based on the input received via the one or moreadministrative interfaces at step 318). At step 320, treasury servicecomputing platform 110 may send the one or more updated configurationsettings to the one or more cash handling devices (e.g., to treasuryservice cash handling device 140 and/or to one or more other cashhandling devices). For example, at step 320, treasury service computingplatform 110 may send, via the communication interface (e.g.,communication interface 115), and to the at least one cash handlingdevice of the one or more cash handling devices (e.g., treasury servicecash handling device 140), configuration information directing the atleast one cash handling device of the one or more cash handling devices(e.g., treasury service cash handling device 140) to implement the oneor more configuration settings. In some instances, treasury servicecomputing platform 110 may send the configuration information directlyto treasury service cash handling device 140 and/or one or more othercash handling devices, while in other instances, treasury servicecomputing platform 110 may send such configuration information totreasury service cash handling device 140 and/or one or more other cashhandling devices via treasury device support server 150.

As illustrated in greater detail below, treasury service computingplatform 110 also may provide one or more client portal interfaces toone or more client devices (e.g., treasury client computing device 160)and/or one or more client users (who may, e.g., be employees and/oragents of one or more treasury clients of a financial institutionoperating treasury service computing platform 110 and/or treasuryservice cash handling device 140). Such client portal interfaces may,for instance, allow a client user to define and/or update one or moreclient-specific settings, such as client-specific transaction limitsettings, alert settings (e.g., mid-day alerts if no transactions aremade by certain stores), user settings, and/or other settings. Inaddition, treasury service computing platform 110 may update one or morecash handling devices, such as treasury service cash handling device140, and/or support servers, such as treasury device support server 150,in accordance with the settings and/or any changes to the settings.

Referring to FIG. 3F, at step 321, treasury service computing platform110 may receive a request for one or more client management interfaces(e.g., from treasury client computing device 160). For example, at step321, treasury service computing platform 110 may receive, via thecommunication interface (e.g., communication interface), from a clientcomputing device (e.g., treasury client computing device 160), a requestfor a client management portal.

At step 322, treasury service computing platform 110 may provide one ormore client management interfaces (e.g., to treasury client computingdevice 160, based on receiving the request for the one or more clientmanagement interfaces at step 321). For example, at step 322, based onreceiving the request for the client management portal, treasury servicecomputing platform 110 may provide, via the communication interface(e.g., communication interface 115), to the client computing device(e.g., treasury client computing device 160), at least one clientmanagement interface.

For example, in providing the at least one client management interfaceto treasury client computing device 160, treasury service computingplatform 110 may cause, control, and/or direct treasury client computingdevice 160 to display and/or otherwise present a graphical userinterface similar to graphical user interface 1000, which is illustratedin FIG. 10. As seen in FIG. 10, graphical user interface 1000 mayinclude one or more user interface controls and/or other elements thatmay enable a user of treasury client computing device 160 interactingwith graphical user interface 1000 to define and/or update one or moreclient-specific settings for various cash handling devices, such asclient-specific usage limit settings, alert threshold settings, usersettings, and/or other settings. Additionally or alternatively, inproviding the at least one client management interface to treasuryclient computing device 160, treasury service computing platform 110 maycause, control, and/or direct treasury client computing device 160 todisplay and/or otherwise present a graphical user interface similar tographical user interface 1100, which is illustrated in FIG. 11. As seenin FIG. 11, graphical user interface 1100 may include one or more userinterface controls and/or other elements that may enable a user oftreasury client computing device 160 interacting with graphical userinterface 1100 to view one or more reports generated by treasury servicecomputing platform 110 based on cash handling device activityinformation, such as one or more deposit reports, change order reports,store/location reports, and/or other reports.

At step 323, treasury service computing platform 110 may receive inputvia the one or more client management interfaces. For example, at step323, treasury service computing platform 110 may receive, via thecommunication interface (e.g., communication interface 115), from theclient computing device (e.g., treasury client computing device 160),configuration input defining one or more configuration settings for atleast one cash handling device of the one or more cash handling devices(e.g., treasury service cash handling device 140), and the configurationinput may have been received by the client computing device (e.g.,treasury client computing device 160) via the at least one clientmanagement interface (which may, e.g., have been provided to treasuryclient computing device 160 by treasury service computing platform 110at step 322). At step 324, treasury service computing platform 110 maystore one or more updated configuration settings for one or more cashhandling devices (e.g., based on the input received via the one or moreclient management interfaces at step 323).

Referring to FIG. 3G, at step 325, treasury service computing platform110 may send the one or more updated configuration settings to the oneor more cash handling devices (e.g., to treasury service cash handlingdevice 140 and/or to one or more other cash handling devices). Forexample, at step 325, treasury service computing platform 110 may send,via the communication interface (e.g., communication interface 115), andto the at least one cash handling device of the one or more cashhandling devices (e.g., treasury service cash handling device 140),configuration information directing the at least one cash handlingdevice of the one or more cash handling devices (e.g., treasury servicecash handling device 140) to implement the one or more configurationsettings. In some instances, treasury service computing platform 110 maysend the configuration information directly to treasury service cashhandling device 140 and/or one or more other cash handling devices,while in other instances, treasury service computing platform 110 maysend such configuration information to treasury service cash handlingdevice 140 and/or one or more other cash handling devices via treasurydevice support server 150.

As illustrated in greater detail below, treasury service computingplatform 110 also may generate and/or send various reports (e.g., basedon cash handling device activity information, via one or moreinterfaces, portals, email communications, and/or the like) to varioususers and/or devices (e.g., administrative computing device 130,treasury client computing device 160, and/or other devices). Forexample, treasury service computing platform 110 may generate one ormore administrative reports and/or one or more client reportsidentifying what deposits and/or change orders were made, who made them,when they were made, what the denominational breakdown was, whetherthere were any rejected notes or unauthenticated notes, and/or otherinformation. Additionally or alternatively, such reports (which may,e.g., be generated by treasury service computing platform 110) mayinclude information about usage patterns and/or trends in when depositsand/or change orders are made. Treasury service computing platform 110may, for instance, generate some reports specific to an administrativeuser (e.g., of administrative computing device 130) that may includeinformation identifying when particular cash handling devices are busyand/or not busy, when a transport carrier restocked particular cashhandling devices, whether any large deposits or large denominationdeposits (which may, e.g., need to be reported for compliance purposes)occurred, and/or the like.

At step 326, treasury service computing platform 110 may generate one ormore reports (e.g., based on the activity information received at step301). For example, at step 326, treasury service computing platform 110may generate one or more reports based on the aggregated activityinformation comprising the plurality of transaction records receivedfrom the one or more cash handling devices (e.g., treasury service cashhandling device 140). At step 327, treasury service computing platform110 may provide the one or more reports (e.g., to administrativecomputing device 130, treasury client computing device 160, and/or oneor more other computing devices). For example, at step 327, treasuryservice computing platform 110 may provide, via the communicationinterface (e.g., communication interface 115), to at least one computingdevice (e.g., administrative computing device 130, treasury clientcomputing device 160), the one or more reports generated based on theaggregated activity information comprising the plurality of transactionrecords received from the one or more cash handling devices (e.g.,treasury service cash handling device 140).

For example, in providing the one or more reports generated based on theaggregated activity information to administrative computing device 130and/or treasury client computing device 160, treasury service computingplatform 110 may cause, control, and/or direct administrative computingdevice 130 and/or treasury client computing device 160 to display and/orotherwise present a graphical user interface similar to graphical userinterface 1200, which is illustrated in FIG. 12. As seen in FIG. 12,graphical user interface 1200 may include one or more user interfacecontrols and/or other elements that may enable a user of administrativecomputing device 130 and/or treasury client computing device 160interacting with graphical user interface 1200 to view, edit, and/orotherwise access information associated with one or more deposittransactions performed at a particular cash handling device (e.g.,treasury service cash handling device 140).

Additionally or alternatively, in providing the one or more reportsgenerated based on the aggregated activity information to administrativecomputing device 130 and/or treasury client computing device 160,treasury service computing platform 110 may cause, control, and/ordirect administrative computing device 130 and/or treasury clientcomputing device 160 to display and/or otherwise present a graphicaluser interface similar to graphical user interface 1300, which isillustrated in FIG. 13. As seen in FIG. 13, graphical user interface1300 may include one or more user interface controls and/or otherelements that may enable a user of administrative computing device 130and/or treasury client computing device 160 interacting with graphicaluser interface 1300 to view, edit, and/or otherwise access informationassociated with one or more change order transactions performed at aparticular cash handling device (e.g., treasury service cash handlingdevice 140).

As illustrated in greater detail below, after applying provisionalcredit to one or more accounts in connection with one or more deposittransactions, treasury service computing platform 110 may subsequentlyreceive reconciliation information (e.g., from administrative computingdevice 130) based on deposits being physically counted and/or manuallyverified after being transported to and/or received by a financialinstitution operating treasury service computing platform 110 and/ortreasury service cash handling device 140. Based on receiving suchreconciliation information, treasury service computing platform 110 may,for instance, control and/or direct account management computer system120 to convert one or more provisional credits into non-provisionalcredits and/or may revoke one or more previously applied provisionalcredits for non-verified funds.

At step 328, treasury service computing platform 110 may receivereconciliation information (e.g., from administrative computing device130 and/or from one or more other computing devices). For example, atstep 328, treasury service computing platform 110 may receive, via thecommunication interface (e.g., communication interface 115), from anadministrative computing device (e.g., administrative computing device130), reconciliation information associated with at least one deposittransaction completed at the one or more cash handling devices (e.g.,treasury service cash handling device 140).

Referring to FIG. 3H, at step 329, treasury service computing platform110 may generate one or more account update commands (e.g., based on thereconciliation information received at step 328). For example, at step329, based on receiving the reconciliation information associated withthe at least one deposit transaction completed at the one or more cashhandling devices (e.g., treasury service cash handling device 140),treasury service computing platform 110 may generate one or more accountupdate commands, the one or more account update commands directing theat least one account management computer system (e.g., accountmanagement computer system 120) to convert at least onepreviously-applied provisional credit to non-provisional credit.

At step 330, treasury service computing platform 110 may send the one ormore account update commands to account management computer system 120.For example, at step 330, treasury service computing platform 110 maysend, via the communication interface (e.g., communication interface115), to the at least one account management computer system (e.g.,account management computer system 120), the one or more account updatecommands directing the at least one account management computer system(e.g., account management computer system 120) to convert the at leastone previously-applied provisional credit to non-provisional credit. Forinstance, in this way, treasury service computing platform 110 maycontrol, direct, and/or otherwise cause account management computersystem 120 to convert one or more previously applied provisional creditsinto non-provisional credits (e.g., for verified funds) and/or revokeone or more previously applied provisional credits (e.g., fornon-verified funds).

At step 331, account management computer system 120 may receive the oneor more account update commands from treasury service computing platform110. At step 332, account management computer system 120 may update oneor more accounts (e.g., based on the one or more account update commandsreceived from treasury service computing platform 110). For example, atstep 332, account management computer system 120 may update one or morespecific accounts based on the one or more account credit commandsreceived from treasury service computing platform 110 at step 331.

FIG. 14 depicts an illustrative method for utilizing cash handlingdevices to provide treasury functions and implementing a computingplatform to control a plurality of cash handling devices in accordancewith one or more example embodiments. Referring to FIG. 14, at step1405, a cash handling device having at least one processor, acommunication interface, an item accepting device, an item dispensingdevice, and a memory may receive, from a first user of the cash handlingdevice, a request to perform a deposit transaction at a deploymentlocation of the cash handling device. At step 1410, based on receivingthe request to perform the deposit transaction at the deploymentlocation of the cash handling device, the cash handling device mayreceive, via the item accepting device, at least one deposit item fordeposit at the deployment location of the cash handling device. At step1415, the cash handling device may validate the at least one deposititem received for deposit at the deployment location of the cashhandling device. At step 1420, based on validating the at least onedeposit item received for deposit at the deployment location of the cashhandling device, the cash handling device may generate a deposittransaction record associated with the request to perform the deposittransaction, the deposit transaction record comprising depositinformation directing at least one banking server to apply a provisionalcredit to at least one treasury account associated with the first userof the cash handling device. At step 1425, the cash handling device maysend, via the communication interface, and to the at least one bankingserver, the deposit transaction record.

At step 1430, the cash handling device may receive, from a second userof the cash handling device, a request to perform a change ordertransaction at the deployment location of the cash handling device. Atstep 1435, based on receiving the request to perform the change ordertransaction at the deployment location of the cash handling device, thecash handling device may receive, via the item accepting device, atleast one change order item for exchange at the deployment location ofthe cash handling device. At step 1440, the cash handling device mayvalidate the at least one change order item received for exchange at thedeployment location of the cash handling device. At step 1445, based onvalidating the at least one change order item received for exchange atthe deployment location of the cash handling device, the cash handlingdevice may dispense, via the item dispensing device, one or morecurrency items to complete the change order transaction. At step 1450,the cash handling device may generate a change order transaction recordassociated with the request to perform the change order transaction, thechange order transaction record comprising change order informationdirecting the at least one banking server to update one or moretransaction history records associated with the second user of the cashhandling device. At step 1455, the cash handling device may send, viathe communication interface, and to the at least one banking server, thechange order transaction record.

FIG. 15 depicts another illustrative method for utilizing cash handlingdevices to provide treasury functions and implementing a computingplatform to control a plurality of cash handling devices in accordancewith one or more example embodiments. Referring to FIG. 15, at step1505, a computing platform having at least one processor, a memory, anda communication interface may receive, via the communication interface,and from one or more cash handling devices, aggregated activityinformation comprising a plurality of transaction records. At step 1510,the computing platform may identify one or more deposit transactionsbased on the aggregated activity information comprising the plurality oftransaction records received from the one or more cash handling devices.At step 1515, based on identifying the one or more deposit transactionsbased on the aggregated activity information comprising the plurality oftransaction records received from the one or more cash handling devices,the computing platform may generate one or more account credit commands,the one or more account credit commands directing at least one accountmanagement computer system to apply one or more provisional credits toone or more treasury accounts associated with the one or more deposittransactions. At step 1520, the computing platform may send, via thecommunication interface, to the at least one account management computersystem, the one or more account credit commands directing the at leastone account management computer system to apply the one or moreprovisional credits to the one or more treasury accounts associated withthe one or more deposit transactions.

FIG. 16 depicts another illustrative method for utilizing cash handlingdevices to provide treasury functions and implementing a computingplatform to control a plurality of cash handling devices in accordancewith one or more example embodiments. Referring to FIG. 16, at step1605, a cash handling device having at least one processor, acommunication interface, an item accepting device, an item dispensingdevice, an internal currency scanning system, an internal currencytransport system, one or more currency storage cartridges, and a memorymay receive, from a first user of the cash handling device, a request toperform a deposit transaction at a deployment location of the cashhandling device. At step 1610, based on receiving the request to performthe deposit transaction at the deployment location of the cash handlingdevice, the cash handling device may receive, via the item acceptingdevice, at least one deposit item for deposit at the deployment locationof the cash handling device. At step 1615, the cash handling device mayvalidate the at least one deposit item received for deposit at thedeployment location of the cash handling device. At step 1620, based onvalidating the at least one deposit item received for deposit at thedeployment location of the cash handling device, the cash handlingdevice may generate a deposit transaction record associated with therequest to perform the deposit transaction, the deposit transactionrecord comprising deposit information directing at least one bankingserver to apply a provisional credit to at least one treasury accountassociated with the first user of the cash handling device. At step1625, the cash handling device may send, via the communicationinterface, and to the at least one banking server, the deposittransaction record.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A cash handling device, comprising: at least oneprocessor; a communication interface; an item accepting device; an itemdispensing device; an internal currency scanning system; an internalcurrency transport system; one or more currency storage cartridges; andmemory storing computer-readable instructions that, when executed by theat least one processor, cause the cash handling device to: receive, viathe communication interface, and from at least one banking server,configuration information defining one or more configuration settingsfor the cash handling device; store the configuration informationdefining the one or more configuration settings for the cash handlingdevice received from the at least one banking server; receive, from afirst user of the cash handling device, a request to perform a deposittransaction at a deployment location of the cash handling device; basedon receiving the request to perform the deposit transaction at thedeployment location of the cash handling device, receive, via the itemaccepting device, at least one deposit item for deposit at thedeployment location of the cash handling device; validate the at leastone deposit item received for deposit at the deployment location of thecash handling device; based on validating the at least one deposit itemreceived for deposit at the deployment location of the cash handlingdevice, generate a deposit transaction record associated with therequest to perform the deposit transaction, the deposit transactionrecord comprising deposit information directing the at least one bankingserver to apply a provisional credit to at least one treasury accountassociated with the first user of the cash handling device; send, viathe communication interface, and to the at least one banking server, thedeposit transaction record; receive, from a second user of the cashhandling device, a request to perform a change order transaction at thedeployment location of the cash handling device; based on receiving therequest to perform the change order transaction at the deploymentlocation of the cash handling device, receive, via the item acceptingdevice, at least one change order item for exchange at the deploymentlocation of the cash handling device; validate the at least one changeorder item received for exchange at the deployment location of the cashhandling device; based on validating the at least one change order itemreceived for exchange at the deployment location of the cash handlingdevice, dispense, via the item dispensing device, one or more currencyitems to complete the change order transaction; generate a change ordertransaction record associated with the request to perform the changeorder transaction, the change order transaction record comprising changeorder information directing the at least one banking server to updateone or more transaction history records associated with the second userof the cash handling device; and send, via the communication interface,and to the at least one banking server, the change order transactionrecord, wherein the configuration information defining the one or moreconfiguration settings for the cash handling device received from the atleast one banking server and stored by the cash handling device definesone or more usage limits comprising a first maximum deposit amount for afirst client of an organization associated with the cash handling deviceand a second maximum deposit amount for a second client of theorganization associated with the cash handling device, the secondmaximum deposit amount for the second client being different from thefirst maximum deposit amount for the first client, wherein validatingthe at least one deposit item received for deposit at the deploymentlocation of the cash handling device comprises enforcing the one or moreusage limits defined by the configuration information stored by the cashhandling device, and wherein validating the at least one change orderitem received for exchange at the deployment location of the cashhandling device comprises enforcing the one or more usage limits definedby the configuration information stored by the cash handling device. 2.The cash handling device of claim 1, wherein validating the at least onedeposit item received for deposit at the deployment location of the cashhandling device comprises: scanning, by the internal currency scanningsystem, one or more deposit items received for deposit; sorting, by theinternal currency transport system, the one or more deposit itemsreceived for deposit; and physically storing, by the internal currencytransport system, in the one or more currency storage cartridges, theone or more deposit items received for deposit.
 3. The cash handlingdevice of claim 2, wherein validating the at least one change order itemreceived for exchange at the deployment location of the cash handlingdevice comprises: scanning, by the internal currency scanning system,one or more change order items received for exchange; sorting, by theinternal currency transport system, the one or more change order itemsreceived for exchange; and physically storing, by the internal currencytransport system, in the one or more currency storage cartridges, theone or more change order items received for exchange.
 4. The cashhandling device of claim 3, wherein the deployment location of the cashhandling device is a retail banking center operated by a financialinstitution.
 5. The cash handling device of claim 3, wherein thedeployment location of the cash handling device is a shopping mall inwhich a plurality of retailers operate retail stores.
 6. The cashhandling device of claim 3, wherein the at least one deposit itemreceived for deposit comprises one or more currency notes.
 7. The cashhandling device of claim 3, wherein the at least one deposit itemreceived for deposit comprises one or more currency coins.
 8. The cashhandling device of claim 3, wherein the at least one deposit itemreceived for deposit comprises one or more checks.
 9. The cash handlingdevice of claim 3, wherein the deposit information directs the at leastone banking server to credit the at least one treasury accountassociated with the first user of the cash handling device with anamount of funds associated with the at least one deposit item receivedfor deposit at the deployment location of the cash handling device andvalidated by the cash handling device.
 10. The cash handling device ofclaim 3, wherein the at least one change order item received forexchange comprises one or more currency notes.
 11. The cash handlingdevice of claim 3, wherein the at least one change order item receivedfor exchange comprises one or more currency coins.
 12. The cash handlingdevice of claim 3, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the cash handling device to: receive, from a third userof the cash handling device, input defining one or more additionalconfiguration settings for the cash handling device; and storeadditional configuration information based on receiving the inputdefining the one or more additional configuration settings for the cashhandling device from the third user of the cash handling device.
 13. Thecash handling device of claim 1, wherein the one or more usage limitscomprise a maximum change order amount for a third client of theorganization associated with the cash handling device.
 14. The cashhandling device of claim 1, wherein enforcing the one or more usagelimits defined by the configuration information stored by the cashhandling device comprises enforcing a maximum exchange limit defining amaximum amount of currency that is exchangeable by one user of the cashhandling device in one transaction.
 15. A method, comprising: at a cashhandling device comprising at least one processor, a communicationinterface, an item accepting device, an item dispensing device, aninternal currency scanning system, an internal currency transportsystem, one or more currency storage cartridges, and a memory:receiving, by the cash handling device, via the communication interface,and from at least one banking server, configuration information definingone or more configuration settings for the cash handling device;storing, by the cash handling device, the configuration informationdefining the one or more configuration settings for the cash handlingdevice received from the at least one banking server; receiving, by thecash handling device, from a first user of the cash handling device, arequest to perform a deposit transaction at a deployment location of thecash handling device; based on receiving the request to perform thedeposit transaction at the deployment location of the cash handlingdevice, receiving, by the cash handling device, via the item acceptingdevice, at least one deposit item for deposit at the deployment locationof the cash handling device; validating, by the cash handling device,the at least one deposit item received for deposit at the deploymentlocation of the cash handling device; based on validating the at leastone deposit item received for deposit at the deployment location of thecash handling device, generating, by the cash handling device, a deposittransaction record associated with the request to perform the deposittransaction, the deposit transaction record comprising depositinformation directing the at least one banking server to apply aprovisional credit to at least one treasury account associated with thefirst user of the cash handling device; sending, by the cash handlingdevice, via the communication interface, and to the at least one bankingserver, the deposit transaction record; receiving, by the cash handlingdevice, from a second user of the cash handling device, a request toperform a change order transaction at the deployment location of thecash handling device; based on receiving the request to perform thechange order transaction at the deployment location of the cash handlingdevice, receiving, by the cash handling device, via the item acceptingdevice, at least one change order item for exchange at the deploymentlocation of the cash handling device; validating, by the cash handlingdevice, the at least one change order item received for exchange at thedeployment location of the cash handling device; based on validating theat least one change order item received for exchange at the deploymentlocation of the cash handling device, dispensing, by the cash handlingdevice, via the item dispensing device, one or more currency items tocomplete the change order transaction; generating, by the cash handlingdevice, a change order transaction record associated with the request toperform the change order transaction, the change order transactionrecord comprising change order information directing the at least onebanking server to update one or more transaction history recordsassociated with the second user of the cash handling device; andsending, by the cash handling device, via the communication interface,and to the at least one banking server, the change order transactionrecord, wherein the configuration information defining the one or moreconfiguration settings for the cash handling device received from the atleast one banking server and stored by the cash handling device definesone or more usage limits comprising a first maximum deposit amount for afirst client of an organization associated with the cash handling deviceand a second maximum deposit amount for a second client of theorganization associated with the cash handling device, the secondmaximum deposit amount for the second client being different from thefirst maximum deposit amount for the first client, wherein validatingthe at least one deposit item received for deposit at the deploymentlocation of the cash handling device comprises enforcing the one or moreusage limits defined by the configuration information stored by the cashhandling device, and wherein validating the at least one change orderitem received for exchange at the deployment location of the cashhandling device comprises enforcing the one or more usage limits definedby the configuration information stored by the cash handling device. 16.The method of claim 15, wherein validating the at least one deposit itemreceived for deposit at the deployment location of the cash handlingdevice comprises: scanning, by the internal currency scanning system,one or more deposit items received for deposit; sorting, by the internalcurrency transport system, the one or more deposit items received fordeposit; and physically storing, by the internal currency transportsystem, in the one or more currency storage cartridges, the one or moredeposit items received for deposit.
 17. The method of claim 16, whereinvalidating the at least one change order item received for exchange atthe deployment location of the cash handling device comprises: scanning,by the internal currency scanning system, one or more change order itemsreceived for exchange; sorting, by the internal currency transportsystem, the one or more change order items received for exchange; andphysically storing, by the internal currency transport system, in theone or more currency storage cartridges, the one or more change orderitems received for exchange.
 18. The method of claim 15, wherein the oneor more usage limits comprise a maximum change order amount for a thirdclient of the organization associated with the cash handling device. 19.The method of claim 15, wherein enforcing the one or more usage limitsdefined by the configuration information stored by the cash handlingdevice comprises enforcing a maximum exchange limit defining a maximumamount of currency that is exchangeable by one user of the cash handlingdevice in one transaction.
 20. One or more non-transitorycomputer-readable media storing instructions that, when executed by acash handling device comprising at least one processor, a communicationinterface, an item accepting device, an item dispensing device, aninternal currency scanning system, an internal currency transportsystem, one or more currency storage cartridges, and a memory, cause thecash handling device to: receive, via the communication interface, andfrom at least one banking server, configuration information defining oneor more configuration settings for the cash handling device; store theconfiguration information defining the one or more configurationsettings for the cash handling device received from the at least onebanking server; receive, from a first user of the cash handling device,a request to perform a deposit transaction at a deployment location ofthe cash handling device; based on receiving the request to perform thedeposit transaction at the deployment location of the cash handlingdevice, receive, via the item accepting device, at least one deposititem for deposit at the deployment location of the cash handling device;validate the at least one deposit item received for deposit at thedeployment location of the cash handling device; based on validating theat least one deposit item received for deposit at the deploymentlocation of the cash handling device, generate a deposit transactionrecord associated with the request to perform the deposit transaction,the deposit transaction record comprising deposit information directingthe at least one banking server to apply a provisional credit to atleast one treasury account associated with the first user of the cashhandling device; send, via the communication interface, and to the atleast one banking server, the deposit transaction record; receive, froma second user of the cash handling device, a request to perform a changeorder transaction at the deployment location of the cash handlingdevice; based on receiving the request to perform the change ordertransaction at the deployment location of the cash handling device,receive, via the item accepting device, at least one change order itemfor exchange at the deployment location of the cash handling device;validate the at least one change order item received for exchange at thedeployment location of the cash handling device; based on validating theat least one change order item received for exchange at the deploymentlocation of the cash handling device, dispense, via the item dispensingdevice, one or more currency items to complete the change ordertransaction; generate a change order transaction record associated withthe request to perform the change order transaction, the change ordertransaction record comprising change order information directing the atleast one banking server to update one or more transaction historyrecords associated with the second user of the cash handling device; andsend, via the communication interface, and to the at least one bankingserver, the change order transaction record, wherein the configurationinformation defining the one or more configuration settings for the cashhandling device received from the at least one banking server and storedby the cash handling device defines one or more usage limits comprisinga first maximum deposit amount for a first client of an organizationassociated with the cash handling device and a second maximum depositamount for a second client of the organization associated with the cashhandling device, the second maximum deposit amount for the second clientbeing different from the first maximum deposit amount for the firstclient, wherein validating the at least one deposit item received fordeposit at the deployment location of the cash handling device comprisesenforcing the one or more usage limits defined by the configurationinformation stored by the cash handling device, and wherein validatingthe at least one change order item received for exchange at thedeployment location of the cash handling device comprises enforcing theone or more usage limits defined by the configuration information storedby the cash handling device.